Optimizing user equipment operation by conditioning multiple policies on information elements

ABSTRACT

A method for optimizing operation of a user equipment (UE) in a wireless communications network. The method, performed at a network function (NF), comprises: transmitting along the network at least one rule of at least one policy that governs how the UE exchanges packets along the network and that contains information conditioned on at least one information element, such that: if the information conditioned on the at least one information element is contained in the at least one rule and the UE does not satisfy the information contained in the at least one rule, the UE is precluded from exchanging packets in accordance with the at least one rule; if the information conditioned on the at least one information element is contained in the at least one rule and the UE satisfies the information contained in the at least one rule, the UE exchanges packets in accordance with any constraints contained in the at least one rule; and if there is no information in the at least one rule corresponding to the at least one information element, the UE exchanges packets in accordance with any constraints contained in the at least one rule.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority to U.S. ProvisionalApplication Ser. No. 62/688,996 filed Jun. 22, 2018, the contents ofwhich are hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates to wireless communications and particularembodiments or aspects relate to optimizing operation of user equipmentin wireless communication networks in accordance therewith.

BACKGROUND

Network slicing is a capability intended to bring network resourceutilization efficiency, deployment flexibility and support fast growingover-the-top (OTT) applications and services. The Third GenerationPartnership Project (3GPP) is incurring considerable effort to developcomprehensive network slice-related standards in various working groups,including without limitation, the SA2 (architecture) working group,which is responsible for overall system architecture. The 3GPP SA2Working Group is working on specification of the 5G Core (5GC)architecture, including network slicing as a feature. Its TechnicalSpecification (TS) TS-503 defines the Policy and Charging ControlFramework for the 5G System.

One mechanism that is being proposed in support of the Policy andCharging Control Framework is a Network Data Analytics function (NWDAF),such as is discussed in U.S. patent application Ser. No. 15/898,444filed Feb. 17, 2018 by DAO, Ngoc Dung et al. and entitled “System andMethod of Network Policy Optimization”, which is incorporated byreference in its entirety herein. The NWDAF is proposed for use tooptimize the operation of 5G networks such as traffic routing, mobilitymanagement, interaction with control plane (CP) functions (CPFs)including without limitation, the session management function (SMF) 92(FIG. 2), the policy and control function (PCF) 201 (FIG. 2), the accessand mobility management function (AMF) 90 (FIG. 2), the networkrepository function (NRF) 98 (FIG. 2) and/or operation, administrationand maintenance (OAM) functions and/or third party functions. However,this mechanism does not completely address how operation of a userequipment (UE) 52 (FIG. 1) may be impacted.

The PCF 201 may manage and/or optimize one or more policies that governUE operation, including without limitation, a policy that allows the UE52 to select one or multiple routes over which to send and/or receivedata, including without limitation, a UE route selection policy (URSP),a policy that allows the UE 52 to discover and/or select an appropriateaccess network (AN), including without limitation, an access networkdiscovery & selection policy (ANDSP), a policy that allows the UE 52 tosend a large amount of data to an application server (AS) in the datanetwork 88 (DN), including without limitation, a UE background datatransfer policy (UBDTP), a policy that allows the UE 52 to select one ormore specific routes over which to send data of multiple quality ofservice (QoS) flows of a common protocol data unit (PDU) session and/ordata of a QoS flow to the AS, including without limitation, an accesstraffic steering, switching and splitting (ATSSS) policy, a quality ofservice (QoS) policy that allows the UE 52 to send and/or receive datapackets with predefined QoS parameters and/or a policy that allows theUE 52 to send and/or receive data with a specific charging rate and/orconsumption limit, including without limitation, a spending policy.

The URSP may govern how a UE 52 to determine how to route outgoingtraffic, such as, without limitation, by establishing a new PDU session,routing to an established PDU session, off-loading to a non-3GPP ANoutside a PDU session and/or to select a network slice identified by oneor more single network slice selection assistance information (S-NSSAI,collectively NSSAI).

The ANDSP may govern how a UE 52 to select non-3GPP ANs and/or decidehow to route traffic between a selected 3GPP AN and a non-3GPP AN.

The UBDTP is intended to govern how a UE 52 may send background datagathered by the UE to an AS. Background data is data that is sent to theAS but has little or no urgency, so that the background data is notnecessarily sent immediately. On the other hand, the volume ofbackground data could potentially be very large

One non-limiting example of background data is in the context of vehicleto network (V2X) UEs 52. Such V2X UEs 52 may collect sensor data forfault diagnostics and/or vehicle-mounted camera photos of roadconditions that may be used to build a 2D or 3D map of the roads.

The UBDTP is based on the proposition that the background data may besent by the UE 52 when the network load is low.

Conventionally, an application function (AF) 104 (FIG. 3) may negotiatewith the network to identify a time window and a location during whichbackground data may be transferred. In such an approach, the AF 104 mayuse a proprietary solution to send the time window to the UE 52. Such asolution may involve a considerable signalling and network load toconvey this information to the UE 52.

Alternatively, it has been proposed that the network could interactdirectly with the UE 52 in order to communicate the UBDTP to the UE 52.Such a proposal is promising but lacks information on mechanisms thatgovern how the UE 52 would select a network slice, and/or radio accesstechnology (RAT), and/or access network (AN) and what packet filterwould be used for QoS support. Further, at present, there is no methodthat allows the mobile network to enforce the UBDTP.

The ATSSS policy governs how a UE 52 can use multiple ANs to establish aPDU session. The AN may be a non-3GPP AN such as, without limitation, aWi-Fi AN or a fixed AN and/or a 3GPP AN such as, without limitation, a4G and/or 5G radio AN (RAN or (R)AN) 84 (FIG. 2). When a PDU session isallowed to send PDUs across multiple ANs, a packet handling entity in aUE 52 could select a specific AN to send uplink (UL) packets of one or amultiple of QoS flows. In some examples, the packet handling entitycould send a certain percentage of packets to one AN and anotherpercentage of packets to another AN.

The QoS policy may comprise one or more QoS flows and supports QoS flowsthat involve a guaranteed flow bit rate (GBR), those that do not involvea GBR and/or reflective QoS. A QoS flow represents the finestgranularity of QoS differentiation within a PDU session and isassociated with a QoS flow identifier (QFI). User plane (UP) 106 traffichaving a common QFI within a PDU session receives the same trafficforwarding (including without limitation, scheduling and/or admissionthreshold) treatment, which is understood and named as service.

A QoS flow is characterized by three elements, namely:

-   a QoS profile provided by an SMF 92 to the AN 84 via the AMF 90;-   one or more QoS rules provided by the SMF 92 to the UE 52 via the    AMF 90 and/or derived by the UE 52 using reflective QoS control; and-   information enabling classification, bandwidth enforcement and    marking of UP traffic conveyed by the SMF 92 to a UP function (UPF)    86 (FIG. 3), including without limitation:    -   one or more UL packet detection rules (PDRs) provided by the SMF        92 containing a UL packet filter set of the service data flow        (SDF) template,    -   one or more downlink (DL) PDRs containing the DL packet filter        set of the SDF template and/or a reflective QoS indication,    -   a PDR precedence value for each UL and/or DL PDR that may, in        some examples be set to a precedence value of a policy and        charging control (PCC) rule;    -   QoS-related rules, and    -   corresponding packet marking information, including without        limitation, the QFI and/or a transport level packet marking        value, which may in some examples be a differentiated services        code point (DSCP) value of an outer IP header.

In 5G networks, a (typically non-GBR) QoS flow associated with a defaultQoS rule is established for a PDU session and remains establishedthroughout the lifetime of the PDU session to provide connectivity tothe UE 52.

Accordingly, there may be a need for mechanisms to optimize operation ofa UE 52 in wireless communication networks, including withoutlimitation, in a background data transfer policy, that is not subject toone or more limitations of the prior art.

This background is intended to provide information that may be ofpossible relevance to the present invention. No admission is necessarilyintended, nor should be construed, that any of the preceding informationconstitutes prior art against the present invention.

SUMMARY

It is an object of the present disclosure to obviate or mitigate atleast one disadvantage of the prior art.

According to a first broad aspect of the present disclosure, there isdisclosed a method for optimizing operation of a UE in a wirelesscommunications network, comprising actions at an NF of the network of:transmitting along the network at least one rule of at least one policythat governs how the UE may exchange packets along the network and thatcontains information conditioned on at least one information element,such that: if the information conditioned on the at least one iscontained in the at least one rule and the UE does not satisfy theinformation contained in the at least one rule, the UE may be precludedfrom exchanging packets in accordance with the at least one rule; if theinformation conditioned on the at least one information element iscontained in the at least one rule and the UE satisfies the informationcontained in the at least one rule, the UE may exchange packets inaccordance with any constraints contained in the at least one rule; andif there is no information in the at least one rule corresponding to theat least one information element, the UE may exchange packets inaccordance with any constraints contained in the at least one rule.

In an embodiment, the at least one information element can comprise alocation element. In an embodiment, the location element can comprise atleast one of a geographical location specified by a 2D and/or a 3Dcoordinate system, a geographical location specified by an identifier ofa geographical zone of a mapping system, a RAN address, a cellidentifier, a TAI, a registration area identifier and/or an indicationthat the at least one rule may always be considered.

In an embodiment, the at least one information can comprise a timeelement. In an embodiment, the time element can comprise at least one ofa time of day, a date, a day of week, a day of month, a month, a year, aperiod specifying at least one of these to start the period and/or atleast one of these to end the period, a recurrence and/or an indicationthat the at least one rule may always be considered.

In an embodiment, the at least one policy can comprise at least one of aURSP, an ANDSP, a UBDTP, an ATSSS policy, a QoS policy an access andmobility management policy and/or a spending policy.

In an embodiment, the at least one information element can be containedin at least one of the URSP rule itself and/or a component of a routeselection descriptor of the URSP rule and the component can comprise atleast one of a SSC mode, a network slice selection, a DNN selection, anon-seamless off-load indication and/or an access type preference.

In an embodiment, the UBDTP policy can specify at least one of a UBDTPidentification phase for identifying whether the at least one UE isentitled to UBDTP service; a UBDTP rules definition phase for definingat least one rule that contains information conditioned on the at leastone information element and the at least one rule can comprise at leastone of a UBDTP rule and/or a URSP rule; a UBDTP AS configuration phasefor identifying the AS associated with the at least one UE receivingUBDTP service; and/or a UBDTP operation phase for providing UBDTPservice to background data transferred by the at least one UE to the ASassociated therewith in accordance with the at least one rule defined inthe UBDTP definition phase.

In an embodiment, the QoS policy can comprise at least one of a QoSprofile of a QoS flow for exchange between an SMF and a RAN nodeconditioned on the at least one information element, a QoS rule forexchange between the SMF and the at least one UE conditioned on the atleast one information element and/or at least one QoS-relatedinformation set for exchange between the SMF and a UPF conditioned onthe at least one information element.

In an embodiment, the access and mobility management policy can compriseat least one TAI for exchange between the NF and an operator through anAMF conditioned on the at least one information element.

In an embodiment, the NF can comprise a PCF.

In an embodiment, the method can further comprise the action ofincluding at least one indication that stipulates whether the at leastone rule will be strictly enforced. In an embodiment, if the indicationstipulates that the at least one rule will be strictly enforced, if theUE does not satisfy the information contained in the at least one rule,the UE is precluded from exchanging packets in accordance with the atleast one rule. In an embodiment, if the indication stipulates that theat least one rule will not be strictly enforced, even if the UE does notsatisfy the information contained in the at least one rule, the UE mayexchange packets in accordance with any constraints contained in the atleast one rule. In an embodiment, if the at least one rule isconsidered, a different criterion can be applied to packets exchanged inaccordance with the at least one rule. In an embodiment, the differentcriterion can be at least one of a different charging rate and/or adifferent QoS.

According to a second aspect of the present disclosure, there isdisclosed an NF of a wireless communications network comprising: aprocessor; and a non-transient memory for storing instructions that whenexecuted by the processor cause the NF to optimize operation of a UE inthe network, by: transmitting along the network at least one rule of atleast one policy that governs how the UE may exchange packets along thenetwork and that contains information conditioned on at least oneinformation element, such that: if the information conditioned on the atleast one information element is contained in the at least one rule andthe UE does not satisfy the information contained in the at least onerule, the UE may be precluded from exchanging packets in accordance withthe at least one rule; if the information conditioned on the at leastone information element is contained in the at least one rule and the UEsatisfies the information contained in the at least one rule, the UE mayexchange packets in accordance with any constraints contained in the atleast one rule; and if there is no information in the at least one rulecorresponding to the at least one information element, the UE mayexchange packets in accordance with any constraints contained in the atleast one rule.

Embodiments have been described above in conjunction with aspects of thepresent disclosure upon which they can be implemented. Those skilled inthe art will appreciate that embodiments may be implemented inconjunction with the aspect with which they are described, but may alsobe implemented with other embodiments of that aspect. When embodimentsare mutually exclusive, or are otherwise incompatible with each other,it will be apparent to those skilled in the art. Some embodiments may bedescribed in relation to one aspect, but may also be applicable to otheraspects, as will be apparent to those of skill in the art.

According to another broad aspect of the invention, a method foroptimizing operation of a user equipment (UE) in a wirelesscommunications network is provided. The method, performed at a networkfunction (NF), comprises: transmitting along the network at least onerule of at least one policy that governs how the UE exchanges packetsalong the network and that contains information conditioned on at leastone information element, such that: if the information conditioned onthe at least one information element is contained in the at least onerule and the UE does not satisfy the information contained in the atleast one rule, the UE is precluded from exchanging packets inaccordance with the at least one rule; if the information conditioned onthe at least one information element is contained in the at least onerule and the UE satisfies the information contained in the at least onerule, the UE exchanges packets in accordance with any constraintscontained in the at least one rule; and if there is no information inthe at least one rule corresponding to the at least one informationelement, the UE exchanges packets in accordance with any constraintscontained in the at least one rule.

In one aspect, at least one information element comprises a locationelement.

In another aspect, the location element comprises at least one of ageographical location specified by a 2D and/or a 3D coordinate system, ageographical location specified by an identifier of a geographical zoneof a mapping system, a RAN address, a cell identifier, a tracking areaidentifier (TAI), a registration area identifier and/or an indicationthat the at least one rule is always considered.

In one aspect, the at least one information element comprises a timeelement.

In one embodiment, the time element comprises at least one of a time ofday, a date, a day of week, a day of month, a month, a year, a periodspecifying at least one of these to start the period and/or at least oneof these to end the period, a recurrence and/or an indication that theat least one rule is always considered.

In another embodiment, the at least one policy comprises at least one ofa UE route selection policy (URSP), an access network discovery &selection policy (ANDSP), a UE background data transfer policy (UBDTP),an access traffic steering, switching and splitting (ATSSS) policy, aquality of service (QoS) policy, an access and mobility managementpolicy and a spending policy.

In one embodiment, the URSP comprises a list of route selectiondescriptors, each route selection descriptor including a route selectiondescriptor precedence value that determines the priority of the routeselection descriptor, and one or more of location information elementand time information element that respectively determine a location(s)and a time period to apply the route selection descriptor.

In another embodiment, the at least one information element is containedin at least one of the URSP rule and a component of a route selectiondescriptor of the URSP rule, the component comprising at least one of asession continuity (SSC) mode, a network slice selection, a data networkname (DNN) selection, and a non-seamless off-load indication and/or anaccess type preference.

In another embodiment, the UBDTP policy specifies at least one of aUBDTP identification phase for identifying whether the at least one UEis entitled to UBDTP service; a UBDTP rules definition phase fordefining at least one rule that contains information conditioned on theat least one information element, the at least one rule comprising atleast one of a UBDTP rule and a URSP rule; and a UBDTP applicationserver (AS) configuration phase for identifying the AS associated withthe at least one UE receiving UBDTP service; and a UBDTP operation phasefor providing UBDTP service to background data transferred by the atleast one UE to the AS associated therewith in accordance with the atleast one rule defined in the UBDTP rules definition phase.

In another embodiment, the QoS policy comprises at least one of a QoSprofile of a QoS flow for exchange between a session management function(SMF) and a radio access network (RAN) node conditioned on the at leastone information element, and a QoS rule for exchange between the SMF andthe at least one UE conditioned on the at least one information elementand at least one QoS-related information set for exchange between theSMF and a user plane (UP) function (UPF) conditioned on the at least oneinformation element.

In another embodiment, the access and mobility management policycomprises at least one tracking area identifier (TAI) for exchangebetween the NF and an operator through an access and mobility managementfunction (AMF) conditioned on the at least one information element.

In another embodiment, the NF comprises a policy and control function(PCF).

In another embodiment, the at least one policy comprises at least one ofa UE route selection policy (USRP) and the PCF creates the URSP usablefor background data transfer.

In another embodiment, the PCF sends to a session management function(SMF) of the network, a set of policy charging and control (PCC) rulesthat include information on handling a UE background data transferservice associated with a PDU session. The PCC rules include at leastone of a time information element and a location information element.

In another embodiment, if at least one of the PCF and a unified datamanagement (UDM) indicate that the UE is entitled to use background datatransfer service, and at least one of the UBDTP and URSP includes atleast one of a location information element and a time informationelement that is not satisfied, the SMF rejects a UE request.

In another embodiment, if UE configuration data indicate that the UE isentitled to use background data transfer service, but at least one ofthe PCF and UDM confirm that at least one of a location informationelement and a time information element is not satisfied, at least one ofthe PCF and the UDM sends a response to the SMF indicating a rejectionindication to a SMF request for data association dedicated to PDUsession establishment being requested by the UE.

In another embodiment, if UE configuration data indicates that the UE isentitled to use background data transfer service, and at least one ofthe PCF and UDM confirm that both location information element and timeinformation element are satisfied, at least one of the PCF and the UDMsends a response to the SMF indicating an acceptance indication to a SMFrequest for data association dedicated to PDU session establishmentbeing requested by the UE.

In another embodiment, the SMF rejects the UE request by sending areject message to the UE via an application management function (AMF) ofthe network, the reject message including a cause that indicates atleast one reason for rejecting the UE request.

In another embodiment, the at least one reason includes at least one of:the UE is not entitled to background data transfer service, a current UElocation does not satisfy a location information element constraint, anda current UE time does not satisfy a time information elementconstraint.

In another embodiment, the UE is entitled to UBDTP service, the SMFestablishes a requested PDU session for transfer of background data.

In another embodiment, the SMF checks at least one of the locationinformation element and the time information element for the PDU sessionto determine if the UE is entitled to the use a PDU session fortransferring background data.

In another embodiment, if the UE is not entitled to use the backgrounddata transfer service, or if the UE is entitled to use the backgrounddata transfer service but at least one of the location informationelement and the time information element constraints is not satisfied,the SMF sends a reject message to the AMF that includes a causeindicating at least one reason that the UE is not entitled to establisha PDU session or activate user plane of an existing PDU session fortransferring the background data.

In another embodiment, if the UE is entitled to the UBDTP service, andthe location and time information element constraints are satisfied, atleast one of the SMF and the PCF monitor the location and timeinformation elements for the duration of the PDU session of thebackground data transfer.

In another embodiment, based on the monitoring, the SMF determines thatat least one of the location information element and the timeinformation element is not satisfied, the SMF initiates a PDU sessionrelease procedure.

In another embodiment, based on the monitoring, the SMF determines thatat least one of the location information element and the timeinformation element is not satisfied, the SMF initiates a user plane(UP) deactivation of a UP connection of an existing PDU session.

In another embodiment, the SMF initiates the PDU session releaseprocedure upon a request of the PCF due to a violation of the at leastone of the time and location information element constraints.

In another embodiment, the at least one of the location informationelement and the time information element constraints is not satisfied asa result of a UE mobility and handover transition.

In another embodiment, the method further comprises including at leastone indication that stipulates whether the at least one rule is strictlyenforced.

In another embodiment, the network includes an application function (AF)that specifies at least one of network area information and time windowinformation, the AF includes the at least one indication as to whetherthe at least one of network area information and time window informationwill be strictly enforced.

In another embodiment, if the indication stipulates that the at leastone rule will be strictly enforced, if the UE does not satisfy theinformation contained in the at least one rule, then the UE is precludedfrom exchanging packets in accordance with the at least one rule.

In another embodiment, if the indication stipulates that the at leastone rule will not be strictly enforced, even if the UE does not satisfythe information contained in the at least rule, the UE exchanges packetsin accordance with any constraints contained in the at least one rule.

In another embodiment, the PCF sends a UE route selection policy (USRP)when a condition pertaining to at least one of a time period and alocation is met.

In another embodiment, when the condition pertaining to at least one ofa time information element and a location information element is met,the UE performs one of establishing a PDU session and activating a UPconnection of an existing PDU session to couple to a data network name(DNN) selection for use of network services provided therein.

In another embodiment, if the UE exchanges packets even though the UEdoes not satisfy the information in the at least one rule, a differentcriterion is applied to packets exchanged in accordance with the atleast one rule.

In another embodiment, the criterion is at least one of a differentcharging rate and a different quality of service (QoS).

In yet another broad aspect of the invention, a network function (NF) ofa wireless communications network is provided. The NF comprises aprocessor; and a non-transient memory for storing instructions that whenexecuted by the processor cause the NF to optimize operation of a userequipment (UE) in the network, by: transmitting along the network atleast one rule of at least one policy that governs how the UE exchangespackets along the network and that contains information conditioned onat least one information element, such that: if the informationconditioned on the at least one information element is contained in theat least one rule and the UE does not satisfy the information containedin the at least one rule, the UE is be precluded from exchanging packetsin accordance with the at least one rule; if the information conditionedon the at least one information element is contained in the at least onerule and the UE satisfies the information contained in the at least onerule, the UE exchanges packets in accordance with any constraintscontained in the at least one rule; and if there is no information inthe at least one rule corresponding to the at least one informationelement, the UE exchanges packets in accordance with any constraintscontained in the at least one rule. A system including the NF is alsoprovided.

Some aspects and embodiments of the present disclosure may provide amethod of optimizing UE operation by conditioning multiple policies onone or more information elements.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of the present disclosure will now be described by reference tothe following figures, in which identical reference numerals indifferent figures indicate identical elements and in which:

FIG. 1 is a block diagram of an electronic device within a computing andcommunications environment that may be used for implementing devices andmethods in accordance with representative examples of the presentdisclosure;

FIG. 2 is a block diagram illustrating a service-based view of a systemarchitecture of a 5GCN;

FIG. 3 is a block diagram illustrating the system architecture of a 5GCNas shown in FIG. 2 from the perspective of reference point connectivity;

FIG. 4 is a signal flow diagram showing example signal flows by which anNEF may negotiate with an H-PCF about transfer policies for futurebackground data transfer according to an example;

FIG. 5 is a flow chart illustrating an example of a method at an NF foroptimizing operation of a UE in a network according to an example.

In the present disclosure, for purposes of explanation and notlimitation, specific details are set forth in order to provide athorough understanding of the present disclosure. In some instances,detailed descriptions of well-known devices, circuits and methods areomitted so as not to obscure the description of the present disclosurewith unnecessary detail.

Accordingly, the system and method components have been representedwhere appropriate by conventional symbols in the drawings, showing onlythose specific details that are pertinent to understanding the examplesof the present disclosure, so as not to obscure the disclosure withdetails that will be readily apparent to those of ordinary skill in theart having the benefit of the description herein.

Any feature or action shown in dashed outline may in some exampleexamples be considered as optional.

DESCRIPTION

FIG. 1 is a block diagram of an electronic device (ED) 52 illustratedwithin a computing and communications environment 100 that may be usedfor implementing the devices and methods disclosed herein. In someexamples, the ED 52 may be an element of communications networkinfrastructure, such as a base station (for example a NodeB, an evolvedNode B (eNodeB or eNB), a next generation NodeB (sometimes referred toas a gNodeB or gNB), a home subscriber server (HSS), a gateway (GW) suchas a packet gateway (PGW) or a serving gateway (SGW) or various othernodes or functions within a core network (CN) or Public Land MobilityNetwork (PLMN). In other examples, the ED 52 may be device that couplesto the network infrastructure over a radio interface, such as a mobilephone, smart phone or other such device that may be classified as a UserEquipment (UE). In some examples, the ED 52 may be a Machine TypeCommunications (MTC) device (also referred to as a machine-to-machine(m2m) device), or another such device that may be categorized as a UEdespite not providing a direct service to a user. In some references, anED 52 may also be referred to as a mobile device, a term intended toreflect devices that connect to a mobile network, regardless of whetherthe device itself is designed for, or capable of, mobility. Specificdevices may utilize all of the components shown or only a subset of thecomponents, and levels of integration may vary from device to device.Furthermore, a device may contain multiple instances of a component,such as multiple processors, memories, transmitters, receivers, etc. TheED 52 typically includes a processor 54, such as a Central ProcessingUnit (CPU) and may further include specialized processors such as aGraphics Processing Unit (GPU) or other such processor, a memory 56, anetwork interface 58 and a bus 60 to connect the components of ED 52. ED52 may optionally also include components such as a mass storage device62, a video adapter 64, and an I/O interface 68 (shown in dashedoutline).

The memory 56 may comprise any type of non-transitory system memory,readable by the processor 54, such as static random access memory(SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM),read-only memory (ROM), or a combination thereof. In an example, thememory 56 may include more than one type of memory, such as ROM for useat boot-up, and DRAM for program and data storage for use whileexecuting programs. The bus 60 may be one or more of any type of severalbus architectures including a memory bus or memory controller, aperipheral bus, or a video bus.

The ED 52 may also include one or more network interfaces 58, which mayinclude at least one of wired network interface and a wireless networkinterface. As illustrated in FIG. 1, a network interface 58 may includea wired network interface to connect to a network 74, and also mayinclude a radio access network interface 72 for connecting to otherdevices over a radio link. When ED 52 is a network infrastructureelement, the radio access network interface 72 may be omitted for nodesor functions acting as elements of the PLMN other than those at theradio edge (e.g. an eNB). When ED 52 is infrastructure at the radio edgeof a network 74, both wired and wireless network interfaces may beincluded. When ED 52 is a wirelessly coupled device, such as a UE, radioaccess network interface 72 may be present and it may be supplemented byother wireless interfaces such as WiFi network interfaces. The networkinterfaces 58 allow the ED 52 to communicate with remote entities suchas those coupled to network 74.

The mass storage 62 may comprise any type of non-transitory storagedevice configured to store data, programs and other information and tomake the data, programs and other information accessible via the bus 60.The mass storage 62 may comprise, for example, one or more of a solidstate drive, hard disk drive, a magnetic disk drive or an optical diskdrive. In some examples, mass storage 62 may be remote to ED 52 andaccessible through use of a network interface such as interface 58. Inthe illustrated example, mass storage 62 is distinct from memory 56where it is included, and may generally perform storage tasks compatiblewith higher latency, but may generally provide lesser or no volatility.In some examples, mass storage 62 may be integrated with a heterogeneousmemory 56.

The optional video adapter 64 and the I/O interface 68 (shown in dashedoutline) provide interface to couple the ED 52 to external input andoutput devices. Examples of input and output devices include a display66 coupled to the video adapter 64 and an I/O device 70 such as atouch-screen coupled to the I/O interface 68. Other devices may becoupled to the ED 52, and additional or fewer interfaces may beutilized. For example, a serial interface such as a Universal Serial Bus(USB) (not shown) may be used to provide an interface for an externaldevice. Those skilled in the art will appreciate that in examples inwhich ED 52 is part of a data center, I/O interface 68 and Video Adapter64 may be virtualized and provided through network interface 58.

In some examples, ED 52 may be a stand-alone device, while in otherexamples ED 52 may be resident within a data center. A data center, aswill be understood in the art, is a collection of computing resources(typically in the form of services) that can be used as a collectivecomputing and storage resource. Within a data center, a plurality ofservices can be coupled together to provide a computing resource poolupon which virtualized entities can be instantiated. Data centers can becoupled with each other to form networks consisting of pooled computingand storage resources coupled to each other by connectivity resources.The connectivity resources may take the form of physical connectionssuch as Ethernet or optical communications links, and in some instancesmay include wireless communication channels as well. If two differentdata centers are coupled by a plurality of different communicationchannels, the links can be combined together using any of a number oftechniques including the formation of link aggregation groups (LAGs). Itshould be understood that any or all of the computing, storage andconnectivity resources (along with other resources within the network74) can be divided between different sub-networks, in some cases in theform of a resource slice. If the resources across a number of coupleddata centers or other collection of nodes are sliced, different networkslices can be created.

FIG. 2 illustrates a service-based architecture 200 for a 5G or Nextgeneration Core Network (5GCN/NGCN/NCN), shown generally at 200. Thisillustration depicts logical connections between nodes and functions,and its illustrated connections should not be interpreted as directphysical connection. ED 52 forms a radio access network connection witha (Radio) Access Network node (R)AN 84, which is coupled to a User Plane(UP) Function (UPF) 86 such as a UP Gateway of a network interface suchas an N3 interface. UPF 86 coupled to a Data Network (DN) 88 over anetwork interface such as an N6 interface. DN 88 may be a data networkused to provide an operator service, or it may be outside the scope ofthe standardization of the Third Generation Partnership Project (3GPP),such as the Internet, a network used to provide third party service, andin some examples DN 88 may represent an Edge Computing network orresources, such as a Mobile Edge Computing (MEC) network. ED 52 alsocouples to the Access and Mobility Management Function (AMF) 90. The AMF90 is responsible for authentication and authorization of accessrequests, as well as mobility management functions. The AMF 90 mayperform other roles and functions as defined by the 3GPP TechnicalSpecification (TS) 23.501. In a service-based view, AMF 90 cancommunicate with other functions through a service-based interfacedenoted as Namf. The Session Management Function (SMF) 92 is a networkfunction (NF) that is responsible for the allocation and management ofIP addresses that are assigned to a UE as well as the selection of a UPF86 (or a particular instance of a UPF 86) for traffic associated with aparticular session of ED 52. The SMF 92 can communicate with otherfunctions, in a service-based view, through a service-based interfacedenoted as Nsmf. The Authentication Server function (AUSF) 94 providesauthentication services to other NFs over a service-based Nausfinterface. A Network Exposure Function (NEF) 96 can be deployed in thenetwork to allow servers, functions and other entities such as thoseoutside a trusted domain to have exposure to services and capabilitieswithin the network. In one such example, the NEF 96 can act much like aproxy between an application server outside the illustrated network andNFs such as the Policy Control Function (PCF) 201, the SMF 92 and theAMF 90, so that the external application server can provide informationthat may be of use in the setup of the parameters associated with a datasession. The NEF 96 can communicate with other NFs through aservice-based Nnef network interface. The NEF 96 may also have aninterface to non-3GPP functions. A Network Repository Function (NRF) 98,provides network service discovery functionality. The NRF 98 may bespecific to the PLMN or network operator, with which it is associated.The service discovery functionality can allow NFs and UEs coupled to thenetwork to determine where and how to access existing NFs, and maypresent the service-based interface Nnrf. PCF 201 communicates withother NFs over a service-based Npcf interface, and can be used toprovide policy and rules to other NFs, including those within thecontrol plane (CP) 108. Enforcement and application of the policies andrules is not necessarily the responsibility of the PCF 201, and isinstead typically the responsibility of the functions to which the PCF201 transmits the policy. In one such example the PCF 201 may transmitpolicy associated with session management to the SMF 92. This may beused to allow for a unified policy framework with which networkbehaviour can be governed. A Unified Data Management Function (UDM) 102can present a service based Nudm interface to communicate with otherNFs, and can provide data storage facilities to other NFs. Unified datastorage can allow for a consolidated view of network information thatcan be used to ensure that the most relevant information can be madeavailable to different NFs from a single resource. This can makeimplementation of other NFs easier, as they do not need to determinewhere a particular type of data is stored in the network. The PCF 201may be associated with the UDM 102 because it may be involved withrequesting and providing subscription policy information to the UDR 401,but it should be understood that typically the PCF 201 and the UDM 102are independent functions. The PCF 201 may have a direct interface tothe UDR 401. The stored data is typically associated with policy profileinformation (which may be provided by PCF 201) that governs the accessrights to the stored data. In some example, the UDR 401 may store policydata, structured data for exposure, application data, as well as usersubscription data which may include any or all of subscriptionidentifiers, security credentials, access and mobility relatedsubscription data and session related data. Application Function (AF)104 represents the non-data plane also referred to as the non-userplane) functionality of an application deployed within a networkoperator domain and within a 3GPP-compliant network. The AF 104interacts with other core NFs through a service-based Naf interface, andmay access network capability exposure information, as well as provideapplication information for use in decisions such as traffic routing.The AF 104 can also interact with functions such as the PCF 201 toprovide application-specific input into policy and policy enforcementdecisions. It should be understood that in many situations the AF 104does not provide network services to other NFs, and instead is oftenviewed as consumer or user of services provided by other NFs. Anapplication function outside the 3GPP network can perform many of thesame functions as AF 104 through the use of NEF 96.

ED 52 communicates with NFs that are in the UP 106, and the CP 108depicted in FIG. 3. The UPF 86 is a part of the CN UP 106 (DN 88 beingoutside the 5GCN). (R)AN 84 may be considered as a part of a UP, butbecause it is not strictly a part of the CN, it is not considered to bea part of the CN UP 106. AMF 90, SMF 92, AUSF 94, NEF 96, NRF 98, PCF201 and UDM 102 are functions that reside within the CN CP 108 and areoften referred to as CP Functions (CPFs). AF 104 may communicate withother functions within CN CP 108 (either directly or indirectly throughthe NEF 96), but is typically not considered to be a part of the CN CP108.

Those skilled in the art will appreciate that there may be a pluralityof UPFs 86 coupled in series between the (R)AN 84 and the DN 88, and aswill be discussed with respect to FIG. 3, multiple data sessions todifferent DNs can be accommodated through the use of multiple UPFs 86 inparallel.

FIG. 3 illustrates a reference point representation of a 5GCNarchitecture 300. For the sake of clarity, some of the NFs illustratedin FIG. 2 are omitted from this figure, but it should be understood thatthe omitted functions and those not illustrated in either FIG. 2 or FIG.3) can interact with the illustrated functions.

ED 52 couples to both (R)AN 84 (in the UP 304) and AMF 90 (in the CP306). The ED-to-AMF connection is an N1 connection. (R)AN 84 alsocouples to the AMF 90, and does so over an N2 connection. The (R)AN 84couples to a UPF function 86 of an N3 connection. The UPF 86 isassociated with a PDU session, and couples to the SMF 92 over an N4interface to receive session control information. If the ED 52 hasmultiple PDU sessions active, they can be supported by multipledifferent UPFs 86, each of which is coupled to an SMF 92 over an N4interface. It should be understood that from the perspective ofreference point representation, multiple instances of either an SMF 92or an UPF 86 are considered as distinct entities. The UPFs 86 eachcouple to at least a DN 88 outside the 5GCN over an N6 interface. SMF 92couples to the PCF 201 over an N7 interface, while the PCF 201 couplesto an AF 104 over an N5 interface. The AMF 90 couples to the UDM 102over an N8 interface. If two UPFs 86 in UP 304 couple to each other,they can do so over an N9 interface. The UDM 102 can couple to an SMF 92over an N10 interface. The AMF 90 and SMF 92 couple to each other overan N11 interface. An N12 interface couples the AUSF 94 to the AMF 90.The AUSF 94 can couple to the UDM 102 over an N13 interface. In networksin which there is a plurality of AMFs 90, they can couple to each otherover an N14 interface. The PCF 201 can couple to an AMF 90 over the N15interface. If there is a plurality of SMFs 92 in the network, they cancommunicate with each other over an N16 interface.

It should also be understood that any or all of the functions and nodes,discussed above with respect to the architectures 200 and 300 of the5GCN, may be virtualized within a network, and the network itself may beprovided as network slice of a larger resource pool, as will bediscussed below.

Introduction of Information Elements

The present disclosure introduces a plurality of information elementsthat may be integrated within a plurality of PCF 201 policies to provideadditional granularity to govern the operation of a UE 52. Accordingly,the PCF 201, with input from the NWDAF for, by way of non-limitingexample, obtaining statistical and/or analytical information of variousnetwork parameters, including without limitation, network traffic load,network slice traffic load, resource utilization, traffic distributionin different network locations, quality of experience (QoE), UE mobilityinformation, UE behavior information and/or QoS, includes one or more ofsuch new information elements as information elements of the various UEpolicies either alone or in combination with each other and/or withother information elements including, without limitation, S-NSSAI, RAT,application ID and/or a packet filter descriptor to provide, guidance tothe UE 52 to optimize its access of the best available networkresources.

The PCF 201 may establish and maintain policies comprising one or morerules incorporating such information elements as parameters thereof andmay send them to the UE 52. In some examples, the rules may be providedto the UE 52 during the initial registration of the UE 52 with thenetwork. In some examples, the rules may be provided to the UE 52 as apolicy update when the UE 52 changes its status such that it isappropriate to provide one or more of such rules to the UE 52. In someexamples, the PCF 201 may provide a policy update to the UE 52 at otherpoints in time, including, without limitation, when one or more of suchrules has been updated. In some examples, depending upon networkloading, the ability of the PCF 201 to provide a policy update to the UE52 may be delayed or obviated entirely. In some examples, the SMF 92 mayprovide one or more rules to the UE 52 (and/or update one or more rulespreviously provided) during PDU session establishment and/or PDU sessionmodification procedures.

The present disclosure contemplates two of such information elements,namely a location element and a time element that may be introducedindividually or collectively into one or more of such policies.

Location Element

The location element indicates a geographic indication of where the UE52 could use a given rule of a given policy. The location element maytake the form, without limitation, of any or all of:

-   a geographical location that may be specified by a 2D and/or a 3D    coordinate system;-   a geographical location that may be specified by a unique identifier    of a geographical zone of a predetermined mapping system. The zone    may overlap another zone or the zones may be non-overlapping. In    some examples, the map may be sent from the 5G core network (CN)    function to the UE 52 by a CP 306 interface, including without    limitation, the N1 interface, or from an AS to the UE 52 over a UP    304 data connection;-   a list of RAN 84 addresses that may, in some examples be internet    protocol (IP) addresses and/or fully qualified domain names (FQDNs);-   an access type that may, in some examples, be a non-3GPP AN such as    Wi-Fi, or a 3GPP AN such as, without limitation, 3G, 4G, 5G and/or    6G RAN 84;-   a list of cell identifiers and/or a list of RAN identifiers that    each identify the identity of a radio node that sends and receives    radio signals to couple a UE 52 to a DN 88;-   a tracking area identifier (TAI) that identifies a tracking area. In    some examples, a tracking area may comprise a list of cell    identifiers and/or a list of RAN node identifiers;-   a registration area identifier that uniquely indicates a specific    registration area. In some examples, the UE 52 may store    registration areas in a local storage. In some examples, the    registration area may comprise a set of tracking areas; and/or-   an indication that the policy rule covered by the location element    is applicable to any location.

Time Element

The time element indicates a date and/or time and/or range thereofduring which the UE 52 could use a given rule of a given policy. Thetime element may take the form, without limitation, of any or all of:

-   a start time of day;-   an end time of day;-   a start date;-   an end date;-   a day (and/or a list of days) of week;-   a day(and/or a list of days) of month;-   a month (and/or a list of months in a year);-   a year (and/or a list of years) and/or a start year and/or an end    year;-   one or more periods that each specify a start and an end time and/or    day and/or a recurrence; and/or-   an indication that the policy rule covered by the time element is    applicable to any time.

It will be appreciated that in addition to the two information elementsidentified, namely the location element and the time element, otherinformation elements may present themselves to those of ordinary skillin this art upon consideration of the present disclosure and withoutdeparting from its scope.

A number of non-limiting examples will now be described showing how thenew information elements may be introduced into rules of variouspolicies that govern how a UE 52 may exchange packets with an AS alongthe network, including without limitation, the policies identifiedabove. It will be appreciated that these are examples only, and thatthese (and other) information elements may be introduced, into these(and other) policies by virtue of the described (and other) examplemechanisms upon consideration of the present disclosure and withoutdeparting from its scope.

For each type of policy, the PCF 201 may transmit one or more policyrules along the network to the UE 52, where each policy rule coversdifferent location information element and/or time information element.The various location information element and/or the time informationelement in various policy rules may be overlapping or non-overlapping.It is understandable that the terminologies “information element” and“element information” are changeable in the embodiments of the presentinvention. For example, the location element information can be named asthe location information element and time element information can benamed as time information element.

The application software in the UE 52 may have a user interface by whichthis information is presented to a user of the UE 52. By viewing thepolicies (and policy rules thereof) using such a user interface, theuser may decide where and when to use one or more network services,including without limitation, voice, video and/or data services. Theuser may also decide when and where to access one or more radio accesstypes, including without limitation, 3GPP ANs and/or non-3GPP ANs. Insome examples, the software in the UE 52 may automatically select anduse network services, including without limitation, 3GPP ANs and/ornon-3GPP ANs and/or network slice(s) based upon the location informationelement and/or the time information element contained in individualpolicy rules.

In some non-limiting examples, the PCF 201 may include one or moreindications, including without limitation, an enforcement indication,that stipulates whether or not the location information element and/orthe time information element will or will not be strictly enforced.

In some non-limiting examples, the PCF 201 may inform the SMF 92 of theapplicable indication(s) for the location information element and/or thetime information element of individual policy rules. In turn, in somenon-limiting examples, the SMF 92 may forward the indication(s) to theUPF 86 and/or to the RAN 84.

In some non-limiting examples, the PCF 201 may include the applicableindication(s) for the location information element and/or the timeinformation element of individual policy rules in the UE policiesthemselves, including without limitation, the URSP.

If the indication(s) stipulate that the location information elementand/or the time information element will be strictly enforced, the UE 52will be precluded from exchanging packets in accordance with the ruleassociated therewith, in that one or more of the UE 52, the UPF 86and/or the RAN 84 will drop packets of PDU session(s) and/or QoS flow(s)that do not satisfy the location information element and/or the timeinformation element.

If the indication(s) stipulate that the location information elementand/or the time information element will not be strictly enforced, oneor more of the UE 52, the UPF 86 and/or the RAN 84 may preclude the UE52 from exchanging packets in accordance with the rule associatedtherewith. Alternatively, one or more of the UE 52, the UPF 86 and/orthe RAN 84 may choose to allow the UE to exchange packets in accordancewith any constraints contained in the rule associated therewith, insteadof precluding the exchange of or dropping of packets of QoS flow(s)and/or PDU session(s) that do not satisfy the location informationelement and/or the time information element. The charging system mayapply a different criterion to the packets that are exchanged eventhought they do not satisfy the location information element and/or thetime information element. In some non-limiting examples, the differentcriterion may be a higher charging rate. Alternatively, the differentcriterion may be that the PCF 201 may have different QoS policies to beapplied to the packets exchanged that do not satisfy the locationinformation element and/or the time information element.

URSP

The PCF 201 provisions the UE 52 with URSP rules of the home PLMN(HPLMN). In some examples, the UE 52 may have been pre-configured withURSP rules by the mobile network operator (MNO) or otherwise. In suchcase, the URSP rules provisioned by the PCF 201 will take precedenceover any pre-configured URSP rules. Additionally, the PCF 201 in theHPLMN may update the URSP rule in the UE 52 when it is roaming. The URSPhas been described at least in 3GPP TS 23.503.

In some examples, the PCF 201 includes the location element and/or thetime element as an information element within the URSP. The locationelement and/or time information element are sent to the UE 52 as part ofone or more of the rules defined incorporating these informationelements.

In some examples, each URSP rule communicated to, and stored in the UE52, has, in addition to a rule precedence value that determines thepriority of the rule within the URSP, one or more of locationinformation element and/or time information element that respectivelydetermine the location(s) and/or the time period(s) to apply the URSPrule. The PCF 201 may provide the UE 52 with one or more URSP rules forrespectively, any location within the network and/or time and/or timeperiod. For each URSP rule, if location information element is provided,the URSP rule may be applied only for the location(s) described by thelocation information element. If no location information element isprovided, the URSP rule may be applied irrespective of the location ofthe UE 52. Similarly, for each URSP rule, if time information element isprovided, the URSP rule may be applied only for the time(s) described bythe time information element. If no time information element isprovided, the URSP rule may be applied irrespective of the time of theUE 52.

Each URSP rule contains a traffic descriptor that determines under whattraffic conditions, the URSP will be applied. The traffic descriptorworks in conjunction with either or both of the location informationelement and/or time information element so that traffic that satisfiesthe traffic descriptor may be sent to the network only when the UE 52 isin a location and/or a time period that respectively satisfies thelocation information element and/or the time information element.Otherwise, even though a packet satisfies the traffic descriptor, one ormore of the UE 52 and/or the UPF 86 may drop it.

Each URSP rule contains a list of route selection descriptors each ofwhich has, in addition to a route selection descriptor precedence valuethat determines the priority of the route selection descriptor, one ormore of location information element and/or time information elementthat respectively determine the location(s) and/or the time period(s) toapply the route selection descriptor. In some examples, the routeselection descriptor may comprise one or more of the followingcomponents:

-   a session and service continuity (SSC) mode that indicates that    traffic of a matching application will be routed via a PDU session    supporting SSC mode. In some examples, the SSC mode may have one or    more of SSC location information element and/or SSC time information    element respectively indicating the location and/or time when the    SCC mode policy may be applied;-   a network slice selection that indicates that traffic of a matching    application will be routed via a PDU session supporting any of the    included S-NSSAIs. In some examples, the network slice selection may    have one or more of network slice selection location information    element and/or network slice selection time information element    respectively indicating the location and/or time when the network    slice selection policy may be applied. In some examples, a mobile    network operator may use the network slice selection location    information element and/or network slice selection time information    element to indicate the availability of network slices at    respectively, certain locations and/or time periods. By way of    non-limiting example, if an URLLC service may be provided by a 5G    RAN 84 along a highway, the network slice selection may include as    network slice selection location information element, a list of RAN    nodes 84 installed along the highway. In another non-limiting    example, the network may be optimized so that when the traffic load    of a certain network slice is low, the network management may turn    off computing hardware associated with such network slice to save    energy and divert the traffic to be handled by other network slices.    In such a scenario, one or more of network slice selection time    information element may be used to indicate only the time period(s)    when the network slice is accessible.-   a data network name (DNN) selection that indicates that the traffic    of a matching application is to be routed via a PDU session    supporting any of the included DNNs. In some examples, the DNN    selection may have one or more of DNN selection location information    element and/or DNN selection time information element to indicate    the location and/or time when the DNN selection policy is to be    applied. In some non-limiting examples, IP multimedia subsystem    (IMS) voice service, IMS video service and/or local area data    network (LADN) service may be available in certain locations and/or    time periods. In such a scenario, a MNO may use the DNN selection    location information element and/or the DNN selection time    information element to so advise the UE 52.-   a non-seamless off-load indication that indicates that traffic of a    matching application is to be off-loaded to a non-3GPP AN outside of    a PDU session. In some examples, the non-seamless off-load    indication may have one or more of non-seamless off-load indication    location information element and/or non-seamless off-load indication    time information element to indicate the location and/or time when    the non-seamless off-load indication may be applied. In some    non-limiting examples, a video stream application may use a non-3GPP    AN at certain locations and/or time periods. In such a scenario, an    MNO may use the non-seamless off-load indication location    information element and/or non-seamless off-load indication time    information element to so advise the UE 52.-   an access type preference that indicates the access type (3GPP or    non-3GPP AN) on which the PDU session should be established. In some    examples, the access type preference may have one or more of access    type preference location information element and/or access type    preference time information element to indicate the location and/or    time when the access type preference is to be enforced. By way of    non-limiting example, a video streaming application may use a    non-3GPP access type at certain locations and/or time periods. In    such a scenario, an MNO may use the access type preference location    information element and/or access type preference time information    element to so advise the UE 52.

In some examples, the SMF 92 may send one or more of locationinformation element and/or time information element, together withrelated information, including without limitation, the S-NSSAI, DNN,application ID, packet filter (including without limitation for IP,Ethernet or unstructured data) to the RAN 84 and/or UPF 86 during PDUsession establishment and/or PDU session modification procedures.

In such examples, the possibility exists that the UE 52 erroneouslysends PDU(s) that satisfy the criteria established by the relatedinformation, but do not satisfy any of the information elementsassociated with the location element (including in its variousincarnations, including without limitation, SSC location informationelement, network slice selection location information element, DNNselection location information element, non-seamless off-load indicationlocation information element and/or access type preference locationinformation element) and/or the time element (including in its variousincarnations, including without limitation, SSC time informationelement, network slice selection time information element, DNN selectiontime information element, non-seamless off-load indication timeinformation element and/or access type preference time informationelement).

In such circumstances, the RAN node 84 and/or the UPF 86 may detect suchpackets and notify the SMF 92. In some non-limiting examples, the RAN 84and/or the UPF 86 may drop such packets if it is stipulated that thelocation information element and/or time information element ofparticular rules are to be strictly enforced. The SMF 92 may then decideto deactivate the UP connection of the PDU session used to carry theoffending PDUs. Alternatively, the SMF 92 may then decide to release thePDU session used to carry the offending PDUs and/or send a notificationmessage to the AMF 90 advising that the UE 52 is sending traffic inviolation of one or more of the location element and/or the timeelement. The AMF 90 may then perform an AN release procedure to causethe UE 52 to enter into a CM-IDLE state. Alternatively, the AMF 90 mayperform a UE deregistration procedure to de-register the UE 52. In thefurther alternative, the AMF 90 may send a mobility management (MM)message along an N1 interface to the UE 52 requesting it to ceasesending traffic in violation of the location element and/or time elementcriteria.

In some examples, a visiting PCF 201 (V-PCF) in a visiting PLMN (VPLMN)may obtain the URSP rules from the HPLMN and modify the location elementand/or the time element to correspond to respective parameters of theHPLMN.

With the introduction of the location element and/or time element asparameters upon which one or more URSP rules may be conditioned, the PCF201 may simultaneously send multiple URSP rules to the UE 52. Thisobviates the PCF 201 having to set up a mechanism to send a URSP rulewhenever it detects that the UE 52 has satisfied the condition(s) setout in either or both of the location element and/or time element and tosend a further URSP rule whenever it detects that the UE 52 no longersatisfies such condition(s), which would otherwise incur considerablenetwork resources and consume considerable UE power in updating the UEpolicies.

Rather, the UE 52 may make use of the location element and/or timeinformation element contained in the URSP rules to derive networkinformation. By way of non-limiting example, and considering only thelocation element in such example, there may be different accesstechnologies (ATs) (including without limitation, 3GPP 4G RAN 84, 3GPP5G RAN 84 and/or non-3GPP ANs) in different geographical areas of thenetwork. The UE 52 may use the information contained in the locationelement and network service availability to select suitablecommunication parameters, as shown in the following non-limiting examplescenarios:

-   The UE 52 knows of the availability of Wi-Fi or 5G RAN 84 in certain    network locations and may also have a map showing the network ATs.    The UE 52 may be relocated by its associated user to a location to    take advantage of a desired RAT (such as going to a location that    offers Wi-Fi and/or 5G RAN 84);-   The UE 52 uses URSP information elements (including without    limitation, the access type preference, the access type preference    location information element and/or DNN selection location    information element), as well as time information element associated    with URSP information elements (including without limitation, SSC    time information element, network slice selection time information    element, DNN selection time information element, non-seamless    off-load indication time information element and/or access type    preference time information element) to activate a suitable    communication interface, such as, by non-limiting example, a 5G RAN    84 interface, when the UE 52 is moved to an area that offers a given    AT. This ability may reduce the time that the UE 52 would otherwise    incur searching for RANs 84 (including without limitation, Wi-Fi    radio nodes, Wi-Fi access points (APs) and/or 4G and/or 5G radio    base stations (BSs));

The UE 52 may know of locations that offer specific services, includingwithout limitation, an LADN. The UE 52 may use the DNN as a proxyindication of availability of an LADN. Furthermore, by using URSPinformation elements associated with the location element (including inits various incarnations, including without limitation, SSC locationinformation element, network slice selection location informationelement, DNN selection location information element, non-seamlessoff-load indication location information element and/or access typepreference location information element) and/or the time element(including in its various incarnations, including without limitation,SSC time information element, network slice selection time informationelement, DNN selection time information element, non-seamless off-loadindication time information element and/or access type preference timeinformation element), the UE 52 may establish a PDU session or activateUP connection of an existing PDU session to couple to the DNN and usethe services provided thereby when the UE 52 enters a location and/ortime period that satisfies such information elements.

ANDSP

In some examples, the PCF 201 includes one or more of the locationelement and the time element as an information element within the ANDSP.The location element and/or time information element are sent to the UE52 as part of one or more of the ANDSP rules defined incorporating theseinformation elements. In some examples, the mechanism may be similar tothat described above in connection with the URSP.

UBDTP

The UBDTP provides network information to the UE 52 that allows the UE52 to request PDU sessions with an appropriate QoS for the upload ofbackground data to an AS located in the DN 88 or connected to the DN 88.

In some examples, the PCF 201 may provide background data transferpolicies to the UE 52 at any time, including without limitation, duringinitial registration of the UE 52, or when the UE 52 changes location.However, network congestion may preclude the provision by the PCF 201 ofa policy update when desired. In some examples, the PCF 201 includes oneor more of the location element and/or the time element as aninformation element within the UBDTP. The location element and/or thetime information element are sent to the UE 52 within the UBDTP. Thisallows the PCF 201 to provide multiple policy rules to the UE 52proactively when network congestion permits.

The UBDTP involves four phases, namely, an identification phase, a rulesdefinition phase, an AS configuration and an operation phase. Thesephases will be discussed separately below.

UBDTP Identification Phase

In the UBDTP identification phase, the CN identifies whether a given UE52 is one for which specification of UBDTP rules is appropriate. Thereare a number of mechanisms by which this identification may be made,including without limitation:

-   the CN and/or OAM function configuring the UE subscription data of    the UE 52 in the UDM 102 and/or UDR 401 to receive UBDTP service,-   the CN and/or OAM function configuring the UE subscription data of    the UE 52 in the PCF 201 to receive UBDTP service,-   the CN receiving a request for UBDTP service from the UE 52, and-   the CN receiving a notification from an AF 104 identifying the UE 52    as receiving UBDTP service.

In a first mechanism, the CN may configure the UE 52 in the UDM 102and/or UDR 401 to receive UBDTP service. In such a mechanism, anindicator may be used to indicate that the UE 52 is to receive UBDTPservice. Such an indicator may be stored in the subscription data of theUE 52 and/or as part of the access and mobility subscription data, inthe UDR 401 and/or UDM 102. In some examples, the indicator may take onvalues that respectively indicate that UBDTP service is allowed ordisallowed.

In such a mechanism, the AMF 90 retrieves the subscription data of theUE 52 from the UDM 102, including the indicator, such as, by aNudm_SDM_Get service operation of the UDM 102, during registration ofthe UE 52. Thereafter, the AMF 90 may perform a policy associationestablishment procedure as disclosed at least in 3GPP TS 23.502 and inparticular, clause 4.16.1.2 thereof. If the indicator indicates thatUBDTP service is allowed, the PCF 201 provides the AMF 90 with UBDTPinformation (which may in some examples be a new set of UBDTP to beadded to the UE 52, or to delete and/or modify an existing set of UBDTPin the UE 52) and the AMF 90 deploys the UBDTP to the UE 52, includingwithout limitation, using a UE 52 update deliver procedure such as isdisclosed at least in 3GPP TS 23.502, and in particular, clause 4.2.4.3thereof.

In some examples, UBDTP service may be allowed or disallowed on anetwork slice instance (NSI) (in some non-limiting examples, representedby an S-NSSAI) basis and/or for an internal group of UEs 52. In such ascenario, the second mechanism, in which the CN configures the UE 52 inthe PCF 201 to receive UBDTP service may be appropriate. In such amechanism, the AMF 90 may send a request to the PCF 201 for UE accessselection and/or PDU session selection information. In some examples,such a request may include the appropriate S-NSSAI and/or internal groupID. The PCF 201 checks the information provided by the AMF 90 and makesa decision as to whether or not to allow UBDTP service to the UE 52,such as, by way of example, a scenario where the S-NSSAI and/or internalgroup ID is associated with UEs that will use UBDTP. If the PCF 201decides to allow UBDTP service, it may provide the AMF 90 with UBDTPinformation as part of the UE access selection and/or PDU sessionselection information, as is disclosed at least in 3GPP TS 23.503, andin particular, clause 6.6 thereof, or as independent applicationinformation and the AMF 90 deploys the UBDTP to the UE 52, includingwithout limitation, using a UE 52 update deliver procedure such as isdisclosed at least in 3GPP TS 23.502, and in particular, clause 4.2.4.3thereof.

In a third mechanism, the UE 52 may send a request to the AMF 90 forUBDTP service during UE registration, such as is disclosed at least in3GPP TS 23.502, and in particular step 1 of clause 4.2.2.2.2 or clause4.2.2.2.3 thereof, but including an indicator that UBDTP service hasbeen requested. The RAN 84 forwards the UE registration request to theAMF 90. The AMF 90 checks to see if the indicator has been included inthe request, and if so, sends the indicator (or another indicatorcorresponding thereto) to the PCF 201 to request UBDTP service. The PCF201 checks the information provided by the AMF 90 and makes a decisionas to whether or not to allow UBDTP service to the UE 52, such as, byway of example, a scenario where the S-NSSAI, internal group ID and/orDNN is associated with UEs 52 that will use UBDTP. If the PCF 201decides to allow UBDTP service, it may provide the AMF 90 with UBDTPinformation as part of the UE access selection and/or PDU sessionselection information or as independent application information and theAMF 90 deploys the UBDTP to the UE 52, including without limitation,using a UE update deliver procedure such as is disclosed at least in3GPP TS 23.502, and in particular, clause 4.2.4.3 thereof.

In a fourth mechanism, the CN may receive a notification from an AF 104identifying the UE 52 as receiving UBDTP service, such as is disclosedat least in 3GPP TS 23.502, and in particular, clause 4.16.7 thereof.

FIG. 4 is an example signal flow diagram shown generally at 400. Thefigure shows communications between a UDR 401, a home PCF (H-PCF 402),an NEF 96 and an AF 104 in a negotiation between the NEF 96 and theH-PCF 402 about the transfer policies, including without limitation, adesired time window, a charging rate (or reference thereto) and/or amaximum aggregated bit rate (such as is disclosed at least in 3GPP TS23.203 and in particular, clause 6.1.16 thereof) for future backgrounddata transfer, such as is disclosed at least in 3GPP TS 23.503 and inparticular clause 6.1.2.4 thereof.

The negotiation may be conducted prior to establishment of a PDU sessionfor the UE 52 and in some examples when the AF 104 initiates a procedureto the NEF 96. Thereafter, the NEF 96 may apply the UBDTP for anindividual UE 52, including without limitation, by invoking aNpcf_PolicyAuthorization_Create and/or a Npcf_PolicyAuthorization_Updateservice operation directly with the PCF 201 and/or indirectly throughthe policy control function (PCF) 201. Such service operation willinclude an indication to request the CN to allow UE(s) 52 to use theUBDTP. In some examples, the AF 104 includes information indicatingwhich UEs 52 will be allowed to use the UBDTP, including withoutlimitation, one or more external UE ID(s), GPSI(s), external groupID(s), S-NSSAI(s), DNN(s), application identifier(s) and/or AF-serviceidentifier(s). In some non-limiting examples, the AF 104 may specifydesired network area information and/or desired time window(s).

In some non-limiting examples, the AF 104 may include one or moreindications as to whether or not the desired network area informationand/or the desired time window(s) will or will not be strictly enforced.If the indication(s) stipulate that the desired network area informationand/or the desired time window(s) will be strictly enforced, the PCF mayspecify one or more of UBDTP for the UE 52 such that the UE 52 will notbe allowed to use the background data transfer service for packets ofPDU session(s) and/or QoS flow(s) that do not satisfy the desirednetwork area information and/or the desired time window(s). If theindication(s) stipulate that the location information element and/or thetime information element will not be strictly enforced, the PCF mayspecify one or more of UBDTP for the UE 52 such that the UE 52 maychoose to send, instead of dropping, packets of PDU session(s) and/orQoS flow(s) that do not satisfy the location information element and/orthe time information element, to have the 5G system apply a differentcharging policy to the PDU session(s) and/or QoS flow(s) that do notsatisfy the location information element and/or the time informationelement and/or to have the PCF 201 apply a different QoS policy to thePDU session(s) and/or QoS flow(s) that do not satisfy the locationinformation element and/or the time information element and/or the SMF92 may send different QoS parameters to the UE 52, RAN 84, and UPF 86 tobe applied to the PDU session(s) and/or QoS flow(s) that do not satisfythe location information element and/or the time information element.

Step 1. The negotiation is commenced when the AF 104 invokes theNnef_BDTPNegotiation_Create service such as is described at least in TS23.502, and in particular, clause 5.2.6.6.2 thereof. In some examples,the AF 104 may include information indicating which UEs 52 will beallowed to use the UBDTP, including without limitation, one or moreexternal UE ID(s), GPSI(s) of UE(s) 52, external group ID(s),S-NSSAI(s), DNN(s), application identifier(s) and/or AF-serviceidentifier(s).

Step 2. In response thereof, the NEF 96 invokes theNpcf_BDTPolicyControl_Create request service with the H-PCF 402, as isdescribed at least in 3GPP TS 23.502, and in particular, clause5.2.5.5.2 thereof, to authorize creation of the UBDTP. If the UE 52information is provided in step 1, the NEF 96 may map the external UE IDto another internal UE ID, such as a SUPI, a subscription concealedidentifier (SUCI) and/or a GPSI and/or may map the external group ID toan internal group ID. In some non-limiting examples, the NEF 96 mayinclude the UE 52 information, after mapping the received UE 52information to internal parameters as discussed above, in theNpcf_BDTPolicyControl_Create request message.

Step 3. The H-PCF 402 may request from the UDR 401 all the storedtransfer policies corresponding to the application service provider(ASP) identifier. The H-PCF 402 may recognize the network slice to whichthe ASP belongs from the ASP identifier. If the List of UE IDs that canuse background data transfer service is provided in step 1, the H-PCF402 forwards the list of UE IDs to the UDR 401. In case only one H-PCF402 is deployed in the PLMN, the transfer policy can be locally storedand no interaction with UDR 401 is required.

Step 4. The UDR 401 provides all the stored transfer policies andcorresponding network area information associated with the ASPidentifier to the H-PCF 401. If the List of UE IDs that can usebackground data transfer service is provided in step 3, the UDR 401marks UE can use background data transfer (BDT) service in the SessionManagement Subscription Data.

Step 5. The H-PCF 402 determines, based on information provided by theAF 104 and other available information one or more transfer policies,including URSP of UBDTP for background data transfer. The maximumaggregated bitrate is not enforced in the network.

Step 6. The H-PCF 402 send the acknowledge message to the NEF 96 withthe acceptable transfer policies and a Background Data TransferReference ID. The NEF 96 forwards the received transfer policies to theAF 104 and stores the Background Data Transfer Reference ID for futureinteraction with the PCF 402.

Step 7. The NEF 96 sends a Nnef_BDTPNegotiation_Create response to theAF 104 to provide one or more background data transfer policies to theAF 104. If the NEF received only one background transfer policy from theH-PCF 402, steps 8-11 are not executed and the flow proceeds to step 12.Otherwise, the flow proceeds to step 8.

Step 8. Ultimately, the AF 104 invokes the Nnef_BDTPNegotiation_Updaterequest service, such as is described at least in 3GPP TS 23.502, and inparticular clause 5.2.6.6.3 thereof, to provide the NEF 96 with one ormore selected UBDTP updates, in some examples, including informationindicating which UE(s) 52 will be allowed to use the UBDTP, includingwithout limitation, one or more external UE ID(s), GPSI(s), externalgroup ID(s), S-NSSAI(s), DNN(s), application identifier(s) and/orAF-service identifier(s).

Step 9. The NEF 96 invokes the Npcf_BDTPolicyControl_Update service toprovide the H-PCF 402 with the selected background data transfer policyand the associated Background Data Transfer Reference ID.

Step 10. The H-PCF 402 sends the acknowledge message to the NEF 96.

Step 11. The NEF 96 sends the acknowledge message to the AF 104. If theNEF 96 receives only one transfer policy, the AF 104 is not required toconfirm.

Step 12. The H-PCF 402 stores the reference ID together with the newtransfer policy and the corresponding network area information in theUDR 401. This step is not executed, when the H-PCF 402 decides tolocally store the transfer policy. If the List of UE IDs that can usebackground data transfer service is provided in step 8, the H-PCF 402forwards the list of UE IDs to the UDR 401 and action to be taken.

Step 13. The UDR 401 sends a response to the H-PCF 402 as itsacknowledgement.

UBDTP Rules Definition Phase

In some examples, rather than sending a UBDTP to the UE 52, the PCF 201may send a URSP policy to the UE 52 which the UE 52 may use to performbackground data transfer to its associated AS. Such URSP may contain atraffic descriptor that matches the application ID, IP descriptor and/ornon-IP descriptor and/or DNN used by the UE 52 to send background datato the associated AS. In some examples, each URSP rule communicated to,and stored in the UE 52, has, in addition to a rule precedence valuethat determines the priority of the rule within the UBDTP, a URSP rulevalue that determines the URSP rule(s) to be applied to the QoS flow(s)and/or PDU session(s) that shall be established to deliver backgrounddata and a DNN selection that determines the DNN to which the UBDTPapplies, one or more of location information element and/or timeinformation element that respectively determine the location(s) and/ortime period(s) to enforce the UBDTP rule. The PCF 201 may provide the UE52 with one or more URSP rules for respectively, any location within thenetwork and/or time and/or time period.

In some non-limiting examples, the PCF 201 may include one or moreindications as to whether or not the location information element and/orthe time information element contained in one or more policy rules willor will not be strictly enforced. These indications may or may not bedecided based on the information provided by the AF 104. If theindication(s) stipulate that the location information element and/or thetime information element will be strictly enforced, the UE 52 will notbe allowed to use the background data transfer service for packets ofPDU session(s) and/or QoS flow(s) that do not satisfy the locationinformation element and/or the time information element. If theindication(s) stipulate that the location information element and/or thetime information element will not be strictly enforced, the UE 52 maychoose to send, instead of dropping, packets of PDU session(s) and/orQoS flow(s) that do not satisfy the location information element and/orthe time information element, to have the 5G system apply a differentcharging policy and/or QoS policy to the traffic that does not satisfythe location information element and/or the time information element.

For each URSP rule, if location information element is provided, theURSP rule may be applied only for the location(s) described by thelocation information element. If no location information element isprovided, the URSP rule may be applied irrespective of the location ofthe UE 52. Similarly, for each URSP rule, if time information element isprovided, the URSP rule may be enforced only for the time(s) describedby the time information element. If no time information element isprovided, the URSP rule may be applied irrespective of the time of theUE 52.

Otherwise, in the UBDTP rules definition phase, the PCF 201 provisionsthe UE 52 with UBDTP rule(s) of the HPLMN. In some examples the UE 52may have been pre-configured with UBDTP rules by the MNO or otherwise.In such case, the UBDTP rules provisioned by the PCF 201 will takeprecedence over any pre-configured UBDTP rules. Additionally, the PCF201 in the HPLMN may update the UBDTP rule in the UE 52 when it isroaming.

In some examples, each UBDTP rule communicated to, and stored in the UE52, has, in addition to a rule precedence value that determines thepriority of the rule within the UBDTP, one or more of locationinformation element and/or time information element that respectivelydetermine the location(s) and/or time period(s) to enforce the UBDTPrule. The PCF 201 may provide the UE 52 with one or more UBDTP rules forrespectively, any location within the network and/or time and/or timeperiod. For each UBDTP rule, if location information element isprovided, the UBDTP rule may be used only for the location(s) describedby the location information element. If no location information elementis provided, the UBDTP rule may be applied irrespective of the locationof the UE 52. Similarly, for each UBDTP rule, if time informationelement is provided, the UBDTP rule may be used only for the time(s)described by the time information element. If no time informationelement is provided, the UBDTP rule may be applied irrespective of thetime the UE 52 sends background data.

In some non-limiting examples, the PCF 201 may include one or moreindications as to whether or not the location information element and/orthe time information element contained in one or more policy rules willor will not be strictly enforced. If the indication(s) stipulate thatthe location information element and/or the time information elementwill be strictly enforced, the UE 52 will not be allowed to use thebackground data transfer service for packets of PDU session(s) and/orQoS flow(s) that do not satisfy the location information element and/orthe time information element. If the indication(s) stipulate that thelocation information element and/or the time information element willnot be strictly enforced, the UE 52 may choose to send, instead ofdropping, packets of PDU session(s) and/or QoS flow(s) that do notsatisfy the location information element and/or the time informationelement, to have the 5G system apply a different charging policy and/orQoS policy to the traffic that does not satisfy the location informationelement and/or the time information element.

In some examples, the PCF 201 includes the location element and/or thetime element as an information element within the UBDTP. The locationinformation element and/or the time information element are sent to theUE 52 as part of one or more of the rules defined incorporating theseinformation elements.

Each UBDTP rule contains a traffic descriptor that determines under whattraffic conditions the UBDTP will be applied, which in some non-limitingexamples, may have a similar form and content as the traffic descriptordescribed above in the context of the URSP. The traffic descriptor worksin conjunction with either or both of the location information elementand/or time information element so that traffic that satisfies thetraffic descriptor may be sent to the network only when the UE 52 is ina location and/or a time period that respectively satisfies the locationinformation element and/or the time information element. Otherwise, eventhough a packet satisfies the traffic descriptor, the UE 52 may drop it.

In some examples, a UBDTP rule with a “match all” traffic descriptor maybe provided. Such a UBDTP rule may be used to route traffic ofbackground data applications that do not match any other more-specificUBDTP rule. As such, it will typically be assigned the lowest availableroute precedence value.

As discussed above, each URSP rule contains a list of route selectiondescriptors. In some examples, the URSP rule structure does not definehow the PCF 201 splits the URSP when it will not be delivered to the UE52 in a single NAS message.

If the CN rejects a PDU session establishment request from the UE 52,the UE 52 may trigger a new PDU session establishment based upon thereason for the rejection and the UBDTP.

The traffic descriptor in the USRP and/or UBDTP, as the case may be,ensures that the UE 52 uses an appropriate network slice instance tosend background data to a preconfigured AS. In this manner, thelikelihood that the UE 52 would abuse the UBDTP to send non-backgrounddata is significantly reduced. Further, this mechanism permits theupload of background data to be potentially charged at a lower rateand/or better QoS, such as at a higher maximum bit rate.

UBDTP AS Configuration Phase

In the UBDTP AS configuration phase, the PCF 201 is provided withinformation that identifies the AS associated with the UE(s) 52receiving UBDTP service, as identified in the UBDTP identificationphase.

The associated AS is identified by AS information that may, in somenon-limiting examples, comprise an AF-service-identifier, an externalapplication identifier, an application identifier, the DNN, an externalgroup ID, a PFD, an IP and/or Ethernet descriptor and/or a data networkaccess identifier (DNAI).

In some examples, if the PCF 201 is provided with an externalapplication identifier, the PCF 201 may map this to an applicationidentifier that is used by UPFs 86 and/or CPFs, including withoutlimitation, the PCF 201 and/or SMF 92. In some examples, the PFD may beidentified by a PFD identifier that may, in some non-limiting examples,be unique in the scope of a particular application identifier. There maybe different PFD types associated with a given application identifier.In some examples, the PFD may comprise, by way of non-limiting examples,a PDF identifier, an IP3-tuple, including without limitation, aprotocol, server side IP address and/or port number, a portion of theURL to be matched, which in some non-limiting examples may be a hostname, or a domain matching criterion. Where an IP 3-tuple is specifiedin a PFD, the PCF 201 may be used to create AS information. In someon-limiting examples, the PFD may be designed to convey a proprietaryextension for a proprietary application traffic detection mechanismagreed-upon by the AF 104 and the MNO.

In some examples, the IP descriptor may comprise one or more IP 3tuple(s), which in some non-limiting examples, may comprise one or moreof a source and/or destination IP address, an IPv6 network prefix,source and/or destination port number(s), a protocol ID of the protocolabove the IP level, a next header type, a type of service (TOS) (IPv4)and/or traffic class (IPv6) and/or mask, a flow label (IPv6), a securityparameter index and/or a packet filter direction.

In some examples, the Ethernet descriptor may comprise one or more of adestination MAC address, an Ethertype as defined in IEEE standard 802.3(which in some non-limiting examples, may indicate an IPv4/IPv6payload), a customer-VLAN tag (C-TAG) and/or service-VLAN tag (S-TAG),priority code point (PCP)/drop eligible indicator (DEI) field as definedin IEEE standard 802.1Q and/or IP 3-tuple(s), which in some non-limitingexamples, may comprise a destination IP address, an IPv6 network prefix,a destination port number and/or a protocol ID for the protocol abovethe IP level.

In some examples, the PCF 201 is provided with one or more DNAIs. OneDNAI is used to indicate a traffic routing profile for data routingbetween the UPF 86 and the AS. The traffic routing profile may beconsidered in the SMF 92 and/or the PCF 201. In some examples, the PCF201 may use the DNAI to get AS information, including withoutlimitation, the IP descriptor and/or Ethernet descriptor.

In some examples, the AS information may be configured by the OAM. Insome examples, an AS provider (ASP) may send the AS information to theCN for UBDTP purposes by means of the signal flow diagram of FIG. 4,subject to the following clarifications:

-   In some examples, the AF 104 may send the AS information to the NEF    96 as part of the Nnef_BDTPNegotiation_Create request, such as is    disclosed in at least 3GPP TS 23.502, and in particular, clause    5.2.6.6.2 thereof and/or Nnef_BDTPNegotiation_Update request, such    as is disclosed in at least 3GPP TS 23.502, and in particular,    clause 5.2.6.3.3 thereof, service operation. In some non-limiting    examples, if the AS information includes an external group ID, the    NEF 96 may replace it with an internal group ID. If the AS    information includes an external application identifier, the NEF 96    may map this to an application identifier that is used by UPFs 86    and/or CPFs, including without limitation, the PCF 201 and/or SMF    92.-   Step 9. In some examples, upon receipt of the AS information as part    of the Nnef_BDTPNegotiation_Create request and/or    Nnef_BDTPNegotiation_Update request service operation, the NEF 96    may send the AS information to the H-PCF 402 as part of the    Npcf_BDTPPolicyControl_Create request and/or    Nnef_BDTPolicyControl_Update request service operation. In some    non-limiting examples, if the AS information includes an external    group ID, the NEF 96 may replace it with an internal group ID. If    the AS information includes an external application identifier, the    H-PCF 402 may map this to an application identifier that is used by    UPFs 86 and/or CPFs, including without limitation, the PCF 201    and/or SMF 92.-   In some examples, in step 5 of FIG. 4 the H-PCF 402 may make one or    more UBDTP decisions, based on information provided by the AF 104    and/or other available information. If the AF 104 provides AS    information, the H-PCF 402 may use this information to create a    traffic descriptor, which in some non-limiting examples may include    an application ID and/or an IP (or non-IP) descriptor for UBDTP    and/or URSP (for background data transfer) service operations. In    some examples, if the H-PCF 402 is provided with an external    application identifier, the H-PCF 402 may map this to an application    identifier that is used by UPFs 86 and/or CPFs, including without    limitation, the PCF 201 and/or SMF 92.

Accordingly, the AF 104 may provide AS information to the mobile networkfor UBDTP purposes. In this manner, the likelihood that the UE 52 wouldabuse the UBDTP to send non-background data is significantly reducedsince the UE 52 would comply with the AS information specified.

UBDTP Operation Phase

In the UBDTP operation phase, the UE(s) 52 identified in the UBDTPidentification phase register with the CN and begin to make use of thebackground data transfer service under the UBDTP.

When the UE 52 performs a UE registration procedure, the AMF 90retrieves the access and mobility subscription data from the UDM 102including, without limitation, by a Nudm_SDM_Get service operation, suchas is disclosed at least in 3GPP TS 23.502, and in particular, clause5.2.3.3.2 thereof. In some examples, the UDM 102 may obtain the UEsubscription data from the UDR 401, including without limitation, anindication that the UE is allowed to UBDTP service. In turn, the UDM 102provides the indication to the AMF 90.

In some examples, the AMF 90 may request the PCF 201 to UE-relatedpolicies, including without limitation, using a policy associationestablishment procedure, such as is disclosed at least in 3GPP TS 23.502and in particular, clause 4.16.1.2 thereof. If the access and mobilitysubscription data includes this indication, the AMF 90 forwards thisindication, or a related indication having a similar meaning to the PCF201.

In some examples, the PCF 201 may have been configured with anindication that the UE 52 belongs to an internal group, is accessing anNSI represented by an S-NSSAI and/or accessing a DNN and/or a UE ID(including without limitation, a GPSI, permanent equipment identifier(PEI) and/or SUPI), that allows the UE 52 to UBDTP service.

If the UE 52 is confirmed as being entitled to UBDTP service, in somenon-limiting examples, the PCF 201 may send the UBDTP (or URSP forbackground data transfer purposes) to the AMF 90. The AMF 90 may theninclude this UBDTP (or URSP) in the acceptance of the registration thatit sends to the UE 52. Alternatively, in some non-limiting examples, theAMF 90 may include the UBDTP (or URSP) in a UE configuration updateprocedure for transparent UE policy delivery to the UE 52, such as isdisclosed at least in 3GPP TS 23.502 and in particular clause 4.2.4.3thereof.

The AF 104 may request the CN to allow the UE 52 to have UBDTP serviceby using the Nnef_BDTPNegotiation_Create (as shown in step 1 of FIG. 4)and/or Nnef_BDTPNegotiation_Update (as shown in step 8 of FIG. 4)service operations of the NEF 96, such as is disclosed at least in 3GPPTS 23.502 and in particular, clause 4.16.7 thereof. The AF 104 mayinclude an indication allowing the UE 52 to have UBDTP service in suchservice operations, as well as information identifying the affectedUE(s) 52. The information identifying the affected UE(s) 52 may in somenon-limiting examples, comprise one or more of an AF-service identifier,an external group ID, NSI represented by an S-NSSAI, a DNN, a UE ID(including without limitation, one or more of a GPSI, PEI, SUPI and/orexternal UE ID) and/or an external application identifier.

In some examples, the NEF 96 may map an external ID to an internal ID,including without limitation, a GPSI to a SUPI, an external group ID toan internal group ID and/or an external application identifier to anapplication identifier.

The NEF 96 may process the request by the AF 104 to allow the UE 52 tohave UBDTP service by using the Npcf_BDTPolicyControl_Create (as shownin step 2 of FIG. 4) and/or Npcf_BDTPolicyControl_Update (as shown instep 9 of FIG. 4) service operations of the PCF 201 to update anexisting UBDTP.

The PCF 201 creates and/or updates one or more new UBDTP (and/or URSPfor background data transfer purposes) rule(s) for background datatransfer by those UEs 52 identified by the AF 104 as shown in step 5 ofFIG. 4.

In some examples, the PCF 201 may provide the UBDTP (and/or USRP)rule(s) to the authorized UE(s) 52 by a UE configuration updateprocedure for transparent UE policy delivery, such as is disclosed atleast in 3GPP TS 23.502 and in particular, clause 4.2.4.3 thereof. Insome examples, the PCF 201 may map an external ID to an internal ID,including without limitation, a generic public subscription identifier(GPSI) to a subscription permanent identifier (SUPI), an external groupID to an internal group ID and/or an external application identifier toan application identifier.

In some non-limiting examples, the UBDTP may include a URSP thatspecifies one or more URSP rule(s) that the UE 52 would follow whenrequesting establishment of a PDU session for transferring backgrounddata. Alternatively, in some non-limiting examples, the PCF 201 maycreate a URSP that may be used for background data transfer. Such URSPmay include one or more of an application identifier allocated tobackground data transfer, a DNN having an associated AS for receivingbackground data transfer and/or an IP or non-IP descriptor thatindicates the information of the AS for receiving background datatransfer (which, in some non-limiting examples, may comprise an IPaddress, a UDP and/or a TCP port).

The CN may detect background data transfer through a number ofmechanisms.

In a first mechanism, the UE 52 sends a service request to the AMF 90indicating background data transfer when it requests a PDU session in amanner similar to the UE-requested PDU session establishment proceduresdisclosed at least in 3GPP TS 23.502 and in particular, clause 4.3.2.2.1thereof for non-roaming scenarios and/or roaming scenarios with localbreakout and/or clause 4.3.2.2.2 thereof for home-routed roamingscenarios, subject to the clarification that when the UE 52 requests aPDU session in step 1 of clause 4.3.2.2.1 and/or step 1 of clause4.3.2.2., the UE 52 may indicate “Background Data Transfer Service” asthe request type in the N1 NAS message to the AMF 90.

In some examples, the AMF 90 may have already obtained the access andmobility policy associated with the UE 52 during the registrationprocedure for the UE 52.

If the access and mobility policy does not contain an indicator allowingthe UE 52 UBDTP service, the AMF 90 may reject the UE 52 request.Alternatively, if the access and mobility policy contains an indicatorallowing the UE 52 UBDTP service, but the UBDTP (and/or URSP) rulecontains a location information element and/or time information elementthat is not satisfied, the AMF 90 may reject the UE 52 request. Ineither case, for example, steps 2 through 12 of clause 4.3.2.2.1 and/orsteps 2 through 14 of clause 4.3.2.2.2 may be omitted. Rather, the AMF90 may send a reject message to the UE 52 in the NAS message to the RAN84 discussed in step 12 of clause 4.3.2.2.1, which the RAN 84 forwardsto the UE 52 in step 13 of clause 4.3.2.2.1.

Otherwise, if the access and mobility policy contains an indicatorallowing the UE 52 UBDTP service and the UBDTP (and/or URSP) rule doesnot contain any location information element and/or time informationelement or contains location information element and/or time informationelement that are satisfied, the AMF 90 stores the PDU session ID andbackground data transfer service for this PDU session ID in the UEcontext and, for example in step 3 of clause 4.3.2.2.1 and/or step 3 ofclause 4.3.2.2.2, the AMF 90 may select an SMF 92 that is in charge ofestablishing a PDU session for carrying the background data transferservice and indicates “Background Data Transfer Service” as the requesttype in the message to the SMF 92.

Depending upon the applicable UBDTP (and/or URSP) rule associated withthe background data transfer service, the AMF 90 may include locationinformation element and/or time information element associated with atleast one or more of the DNN, S-NSSAI(s), access type, RAT type and/orSSC mode.

In a second mechanism, the UE 52 sends a service request to the AMF 90when it requests a PDU session in a manner similar to the UE-requestedPDU session establishment procedures disclosed at least in 3GPP TS23.502 and in particular, clause 4.3.2.2.1 thereof for non-roamingscenarios and/or roaming scenarios with local breakout and/or clause4.3.2.2.2 thereof for home-routed roaming scenarios, subject to thequalification that the UE 52 does not inform the AMF 90 that therequested PDU session is for a background data transfer. Rather, the UE52 requests the SMF 92 to establish the requested PDU session forbackground data transfer, for example by sending to the AMF 90 in step 1of clause 4.3.2.2.1 and/or step 1 of clause 4.3.2.2.2 an N1 SM containerthat indicates “Background Data Transfer Service”. In step 3 of clause4.3.2.2.1 and/or step 3 of clause 4.3.2.2.2, the AMF 90 forwards the N1SM container to the selected SMF 92.

Upon receipt of the request, the SMF 92 checks with the UDM 102 and/orwith the PCF 201 to determine whether the UE 52 is entitled to UBDTPservice. In response, the UDM 102 may send, for example, in step 4 ofclause 4.3.2.2.1 and/or step 7 of clause 4.3.2.2.2, an indicationwhether the UE 52 is entitled to UBDTP service.

If the UE 52 is not entitled to UBDTP service, steps 5 through 10 ofclause 4.3.2.2.1 and/or steps 8 through 13 of clause 4.3.2.2.2 may beomitted.

If the UE 52 is entitled to UBDTP service, the SMF 92 may, in somenon-limiting examples, provide an indication to this effect to the PCF201, for example in steps 7b of clause 4.3.2.2.1 and/or step 9b ofclause 4.3.2.2.2. In response, the PCF 201 may send to the SMF 92 thePCC rules that include information on how to handle UBDTP service forthe PDU session. In some non-limiting examples, this may includelocation information element and/or time information element associatedwith at least one or more of the DNN, S-NSSAI(s), access type, RAT type,SSC mode and/or the charging policy that may indicate, by way ofnon-limiting examples, the maximum data volume for the PDU session.

If either or both of the UDM 102 and/or the PCF 201 indicate that the UE52 is not entitled to UBDTP service, the SMF 92 may reject the UE 52request. Alternatively, if either or both the UDM 102 and the PCF 201indicate that the UE 52 is entitled to UBDTP service, but the UBDTP(and/or URSP) rule contains a location information element and/or timeinformation element that is not satisfied, the SMF 92 may reject the UE52 request. In either case, for example, steps 8 through 10 of clause4.3.2.2.1 and/or steps 2 through 14 of clause 4.3.2.2.2 may be omitted.Rather, the SMF 92 may send a reject message to the UE 52 in the N1 SMcontainer to the AMF 90, for example discussed in step 11 of clause4.3.2.2.1 and/or step 14 of clause 4.3.2.2.2, that includes a cause,indicating the reason that the UE 52 is not entitled to UBDTP service(including, without limitation that the UE 52 is not entitled to UBDTPservice, that the current UE 52 location does not satisfy a locationinformation element constraint and/or that the current UE 52 time doesnot satisfy a time information element constraint).

The AMF 90 forwards the N1 SM container to the RAN 84 in step 12 ofclause 4.3.2.2.1. The RAN 84 forwards the N1 SM container to the UE 52in step 13 of clause 4.3.2.2.1.

If the UE 52 is entitled to UBDTP service, the SMF 92 establishes therequested PDU session for background data transfer and may, in somenon-limiting examples, so advise the AMF 90 by sending an indication tothis effect, associated with the PDU session, to the RAN 84 in an N2 SMinformation message to the AMF 90, for example as discussed in step 11of clause 4.3.2.2.1 and/or step 14 of clause 4.3.2.2.2. If so, the AMF90 may store an indication to this effect for the PDU session. In somenon-limiting examples, the AMF 90 may refer to the UBDTP (and/or URSP)policy for any prevailing location information element and/or timeinformation element constraints. In some non-limiting examples, the N2SM information message may include one or more time information elementfor the PDU session during which it may employ background data transfer.

Once the PDU session for background data transfer has been established,if the time of the UE 52 satisfies one or more time information elementfor the PDU session, the RAN 84 may allow UL and/or DL datatransmission. However, if the time of the UE 52 does not satisfy any ofthe time information element for the PDU session, the RAN 84 may notassign radio resources to the PDU session and/or to a QoS flow that isto be used to deliver background data and/or may request the SMF 92 todeactivate the UP of the PDU session established for background datatransfer. Alternatively, in some non-limiting examples, the RAN 84 mayrequest the SMF 92 to release the PDU session and/or QoS flow that isused to deliver the background data. If the UE 52 has only one PDUsession for background data transfer, the RAN 84 may initiate an ANrelease procedure, such as is discussed at least in 3GPP TS 23.502 andin particular clause 4.2.6 thereof, by which the UE 52 will enter theCM-IDLE state.

As well, if the UE 52 is entitled to UBDTP service and all locationinformation element and/or time information element constraints aresatisfied such that the requested PDU session for background datatransfer has been established, the SMF 92 may send to the UPF 86 anindication that the PDU session is for background data transfer and insome non-limiting examples, may include time information element for thePDU session and/or a QoS flow that is to be used to deliver backgrounddata. If the time of the UE 52 satisfies one or more time informationelement for the PDU session set out in the time information elementprovided by the SMF 92 to the UPF 86, the UPF 86 may allow UL and/or DLdata transmission. However, if the time of the UE 52 does not satisfyany of the time information element for the PDU session set out in thetime information element provided by the SMF 92 to the UPF 86, the UPF86 may drop any UL PDU, may not notify the SMF 92 of the DL PDU and/ormay notify the SMF 92 that the time information element constraints haveexpired and/or that the data volume limit has been reached, so that theSMF 92 may deactivate the UP of the PDU session established forbackground data transfer, such as is discussed at least in 3GPP TS23.502 and in particular, clause 4.3.7 thereof and/or the SMF 92 mayrelease the PDU session established for background data transfer, suchas is discussed at least in 3GPP TS 23.502, and in particular, clause4.3.4 thereof.

When the UE 52 sends a service request to enter the CM-CONNECTED state,it may initiate a UE-triggered service request procedure, such as isdiscussed at least in 3GPP TS 23.502 and in particular, clause 4.3.3.2thereof.

In step 1 of clause 4.3.3.2, the UE 52 may include an indication that itintends to use the UBDTP service. The AMF 90 may check the locationinformation element and/or time information element associated with aUBDTP (and/or URSP) rule associated with background data transfer todetermine if the UE 52 is entitled to UBDTP service. If not, or if theUE 52 is entitled to UBDTP service but at least one of the locationinformation element and/or time information element constraints is notsatisfied, the AMF 90 may deny the service request.

Alternatively, for example in step 1 of clause 4.3.3.2, the UE 52 mayinclude in the service request message to the AMF 90 a list of PDUsessions to be activated, at least one of which may be the PDU sessionpreviously established for background data transfer. The AMF 90 may insuch scenario be aware of the PDU session that has been previouslyestablished for background data transfer, or if not, process each of thePDU sessions in the list. In so doing, the AMF 90 may check the locationinformation element and/or time information element associated with aUBDTP (and/or URSP) rule associated with background data transfer (orgenerally) to determine if the UE 52 is entitled to UBDTP service (orgenerally, to proceed with service operations).

If the UE 52 is not entitled to UBDTP service (or generally, to proceedwith service operations), or if the UE 52 is entitled to UBDTP service(or generally, to proceed with service operations) but at least one ofthe location information element and/or time information elementconstraints is not satisfied, the AMF 90 may deny the service request.

Such denial of the service request may be in the form of an MM NASmessage sent by the AMF 90, for example in step 12 of clause 4.3.3.2,that includes the PDU session status in the AMF 90. The MM NAS messagemay include the PDU session ID that has been rejected by the AMF 90and/or indicate the cause, indicating the reason that the UE 52 is notentitled to UBDTP service (including, without limitation that the UE 52is not entitled to UBDTP service, that the current UE 52 location doesnot satisfy a location information element constraint and/or that thecurrent UE 52 time does not satisfy a time information elementconstraint).

If the UE 52 is entitled to UBDTP service (or generally, to proceed withservice operations) and the location information element and/or timeinformation element constraints are satisfied, the AMF 90 may requestthe SMF 92 to activate the UP connection, for example in step 4 ofclause 4.3.3.2. In so doing, the SMF 92 may check the locationinformation element and/or time information element for the PDU sessionassociated with background data transfer (or generally) to determine ifthe UE 52 is entitled to UBDTP service (or generally, to proceed withservice operations).

If the UE 52 is not entitled to UBDTP service (or generally, to proceedwith service operations), or if the UE 52 is entitled to UBDTP service(or generally, to proceed with service operations) but at least one ofthe location information element and/or time information elementconstraints is not satisfied, the SMF 92 may send a reject message tothe AMF 90, for example in step 11 of clause 4.3.3.2, with a cause,indicating the reason that the UE 52 is not entitled to UBDTP service(including, without limitation that the UE 52 is not entitled to UBDTPservice, that the current UE 52 location does not satisfy a locationinformation element constraint and/or that the current UE 52 time doesnot satisfy a time information element constraint). Thereafter, forexample in step 12 of clause 4.3.3.2, the AMF 90 sends an MM NAS messagethat includes the PDU session status in the AMF 90. The MM NAS messagemay include the PDU session ID that has been rejected by the AMF 90and/or indicate the cause, indicating the reason that the UE 52 is notentitled to UBDTP service (including, without limitation that the UE 52is not entitled to UBDTP service, that the current UE 52 location doesnot satisfy a location information element constraint and/or that thecurrent UE 52 time does not satisfy a time information elementconstraint) sent by the SMF 92 to the AMF 90.

If the UE 52 is entitled to UBDTP service (or generally, to proceed withservice operations) and the location information element and/or timeinformation element constraints are satisfied, the SMF 92 monitors thelocation information element and/or the time information elementspecified for the PDU session established for background data transfer.If at any time, at least one of the location information element and/ortime information element constraints is not satisfied, such as, by wayof non-limiting example, due to mobility and/or handover of the UE 52,the SMF 92 may:

-   initiate a PDU session release procedure such as is described in at    least 3GPP TS 23.502 and in particular clause 4.3.4.2 (UE 52 or    network requested PDU session release for non-roaming and roaming    with local breakout) and/or clause 4.3.4.3 (UE 52 or network    requested PDU session release for home-routed roaming) thereof. The    SMF 92 may release the PDU session associated with background data    transfer based on the request of the UE 52, the AMF 90 (due to a    violation of a location information element and/or time information    element constraint), PCF 201 (due to a violation of a location    information element and/or time information element constraint)    and/or a decision by the SMF 92 to release the PDU session (due to a    violation of a location information element and/or time information    element constraint); or-   initiate a UP deactivation such as is described in at least 3GPP TS    23.502 and in particular clause 4.3.7 (CN-initiated selected    deactivation of UP connection of an existing PDU session) thereof.

ATSSS Policy

In some examples, the PCF 201 includes the location element and/or thetime element as an information element with the ATSSS policy. Thelocation element and/or time information element are sent to the UE 52as part of one or more of the rules defined incorporating theseinformation elements. The UE 52 may thus apply different ATSSS policiesat different locations and/or at different times, which allows forgreater flexibility and a tailored ATSSS policy.

In some non-limiting examples, the PCF 201 may include one or moreindications, including without limitation, an enforcement indication,that stipulates whether or not the location information element and/orthe time information element will or will not be strictly enforced.

In some non-limiting examples, the PCF 201 may inform the SMF 92 of theapplicable indication(s) for the location information element and/or thetime information element of individual policy rules. In turn, in somenon-limiting examples, the SMF 92 may forward the indication(s) to theUPF 86 and/or to the RAN 84.

In some non-limiting examples, the PCF 201 may include the applicableindication(s) for the location information element and/or the timeinformation element of individual policy rules in the ATSSS policy.

If the indication(s) stipulate that the location information elementand/or the time information element will be strictly enforced, one ormore of the UE 52, the UPF 86 and/or the RAN 84 may drop packets of PDUsession(s) and/or QoS flow(s) that do not satisfy the locationinformation element and/or the time information element.

If the indication(s) stipulate that the location information elementand/or the time information element will not be strictly enforced, oneor more of the UE 52, the UPF 86 and/or the RAN 84 may choose to send,instead of dropping, packets of PDU session(s) and/or QoS flow(s) thatdo not satisfy the location information element and/or the timeinformation element. The charging system may apply a different chargingpolicy to the PDU session(s) and/or QoS flow(s) that do not satisfy thelocation information element and/or the time information element. TheSMF may provide different QoS parameters to the UE 52, RAN 84 and/or UPF86 for the PDU session(s) and/or QoS flow(s) that do not satisfy thelocation information element and/or the time information element.

In some examples, the PCF 201 sends ATSSS policy rule(s) to the SMF 92during the PDU session establishment procedure. In some examples, theSMF 92 may send the ATSSS policy rule(s) to the UE 52 in a non-accessstratum (NAS) message along an N1 interface. In some examples, the SMF92 may send the ATSSS policy rule(s) to the UE 52 as part of a QoS rule.

In some examples, the ATSSS policy rule(s) may apply to DL traffic. Insuch examples, the PCF 201 may send DL ATSSS policy rule(s) to the SMF92 during a PDU session establishment procedure or on an ongoing basisfor an established PDU session. In some examples, the SMF 92 may use theDL ATSSS policy rule(s) to establish a DL connection from the UPF 86 toRAN node 84(s) associated with the UE 52. Such DL ATSSS policy rule(s)may contain location information element and/or time information elementin respective location information element and/or time informationelement that allow the SMF 92 to select a RAN node 84 in accordancetherewith.

In some examples, the SMF 92 may send the DL ATSSS policy rule(s) to theUPF 86 including the location information element and/or timeinformation element that allow the UPF 86 to forward DL PDUs to suitableRAN nodes 84 in accordance with the location information element and/ortime information element.

QoS Policy

The QoS Policy has been described at least in 3GPP TS 23.501 and inparticular, clause 5.7 thereof.

In some examples, the when the PDU session is established or modified,the SMF 92 may send one or more QoS profiles for one or more QoS flowsto that the RAN 84 may select a QoS profile that satisfies the locationinformation element and/or time information element specified therein.

In some examples, the QoS profiles may overlap other QoS profiles interms of either or both of the location information element and/or timeinformation element. If a plurality of QoS profiles overlap in terms oftime information element, the RAN 84 may select any one of theoverlapping QoS profiles based on the current traffic load condition inthe RAN node 84. If a plurality of QoS profiles overlap in terms oflocation information element, the RAN 84 may select any one of theoverlapping QoS profiles based on the current traffic load condition inthe RAN node 84, as well as the available resources of the RAN node 84and/or information on the mobility of the UE 52 and advise the SMF 92 ofthe selected QoS profile using an N2 SM message.

Having selected one of the overlapping QoS profiles, the RAN 84 may sendan RRC signalling message to the UE 52 to notify it of the selected QoSparameters.

In some examples, the SMF 92 may send a PDU session modification requestmessage to the UPF 86 to provide it with the selected QoS information.

In some examples, the SMF 92 sends one or more QoS rules associated witha QoS flow to the UE 52 when the PDU session is established or modified,so that the UE 52 may select a suitable QoS profile. In some examples,the SMF 92 sends one or more default QoS rules to the UE 52. In someexamples, the SMF 92 sends the location element and/or the time elementas part of one or more of the QoS rules. The UE 52 may thus applydifferent QoS rules at different locations and/or at different times,which allows for greater flexibility and a tailored QoS policy.

In some examples, the QoS rules may overlap other QoS rules (which insome examples may be default QoS rules) in terms of either or both ofthe location information element and/or the time information element. Ifa plurality of QoS (default) rules overlap in terms of either or both ofthe location information element and/or the time information element,the UE 52 may select any one of the overlapping (default) QoS rulesbased on QoS parameters and the resource assignment information the UE52 receives from the serving RAN node 84, which, in some examples, maybe selected QoS parameters sent by the RAN 84 in the RRC messagediscussed above.

In some examples, the SMF 92 may provide QoS-related information as setsto the UPF 86. In some examples, the SMF 92 sends the locationinformation element and/or the time information element as part of oneor more QoS-related information sets. The UPF 86 may thus applydifferent QoS-related information sets at different locations and/or atdifferent times, to select corresponding QoS parameters, includingwithout limitation, session-aggregated maximum bit rate (Session-AMBR),GFBR, MFBR and/or packet delay budgets for RAN 84 and for UPF 86,maximum data burst volume.

In some examples, the QoS-related information sets may overlap otherQoS-related information sets in terms of either or both of the locationinformation element and/or the time information element. If a pluralityof QoS-related information sets overlap in terms of either or both ofthe location information element and/or the time information element,the UPF 86 may select any one of the overlapping QoS-related informationsets based on the traffic condition and/or the resources available tothe UPF 86.

Having selected one of the overlapping QoS-related information sets, theUPF 86 may send a message to the SMF 92 to notify it of the selectedQoS-related information set. The SMF 92 may then select a QoS profileand/or QoS rule for the QoS flow as a result and may notify the RAN 84and/or the UE 52 of the selected QoS profile and/or QoS rule using thePDF session modification procedure.

With the introduction of the location element and/or time element asparameters upon which one or more QoS profiles, QoS rules and/orQoS-related information sets may be conditioned, the SMF 92 may assignmultiple QoS profiles to the RAN 84, multiple QoS rules to the UE 52 andQoS-related information sets to the UPF 86. This allows the UE 52, UPF86 and/or RAN 84, as the case may be, to select a suitable QoS profilebased on the traffic load, the condition of the wireless channel of theUE 52 and of other UEs 52, the resources of the RAN node 84 that areavailable and/or the condition of the CN, without addition instructionfrom the SMF 92. In particular, use of the location element and/or timeelement in this manner tends to reduce the amount of CP 306 signallingto the UE 52 when the CN is congested. This may especially be the casewhen the UE 52 is a device such as an internet of things (IoT) deviceand/or UEs 52 in vehicles, which may be characterized by having PDUsessions that last for a very long time (even to the point of neverbeing released until the UE 52 is de-registered).

Further, the RAN 84 and/or UPF 86 may use corresponding QoS parametersfor traffic enforcement and/or to detect abnormal behaviour by the UE52.

In addition to the foregoing, the UE 52 may know the QoS availability atvarious locations and/or various times. In some examples, the UE 52 mayhave a user interface and/or application software configured to displayQoS parameters to a user of the UE 52, which allows the user to invokeone or more applications that correspond to the QoS parameters providedby the CN, as shown in the following of non-limiting example scenarios:

-   The user may choose to only use a video streaming application that    involves high data rates, when it is known to the user that the    network can support such high data rates;-   The user may choose to use a video streaming application that can    select a video data rate that corresponds to known QoS parameters,    including without limitation, MFBR, Session-AMBF and/or UE Aggregate    Maximum Bit Rate (UE-AMBR);-   Some devices, including without limitation, IoT devices and/or UEs    52 in vehicles may send UL data when the network can offer higher    data rates, or is less congested.

Access and Mobility Management

In some examples, the PCF 201 sends access and mobility-related policycontrol information to the AMF 90 to enable enforcement of access andmobility policy decision made by the PCF 201 for control of service arearestrictions and RAT/frequency selection policy (RFSP) index. The accessand mobility-related policy has been described at least in 3GPP TS23.503 and in particular clause 6.5 thereof.

Since the UE 52 may exhibit different mobility patterns at differentlocation and/or times, such as, by way of non-limiting example, duringweekdays, weekends, evenings and at night, the access and mobilitymanagement parameters may be conditioned on one or more of locationinformation element and/or time information element and sent to the UE52 so that suitable parameters that satisfy conditions set out in thelocation information element and/or the time information element may beselected by the UE 52.

These parameters employ TAIs that indicate where the UE 52 is allowed(or is not allowed, as the case may be) to be registered. It will thusbe appreciated that, to a certain extent, location information elementis already taken into account by the TAIs in establishing access andmobility management parameters. Accordingly, the discussion below willfocus primarily on the time information element.

The access and mobility-related policy control information comprises alist of allowed TAIs and a list of non-allowed TAIs.

In some examples, each (or in some examples, all) allowed TAI(s) may beassociated with time information element that determines the timeperiod(s) to apply the allowed TAI(s). For each (or all, as the case maybe) allowed TAI(s), if time information element is provided, the (orall, as the case may be) allowed TAI(s) will be enforced only for thetime(s) described by the time information element. If no timeinformation element is provided, the (or all, as the case may be)allowed TAI(s) will be applied irrespective of the time of the UE 52.

In some examples, each (or in some examples, all) non-allowed TAI(s) maybe associated with time information element that determines the timeperiod(s) to apply the non-allowed TAI(s). For each (or all, as the casemay be) non-allowed TAI(s), if time information element is provided, the(or all, as the case may be) non-allowed TAI(s) will be enforced onlyfor the time(s) described by the tie information. If no time informationelement is provided, the (or all, as the case may be) non-allowed TAI(s)will be applied irrespective of the time of the UE 52.

The MNO may make use of the time information element for each (or insome examples, all) allowed TAI(s). By way of non-limiting example, theexpected behaviour of a UE 52 may be to send UL data at a scheduledtime, such as, without limitation, between midnight and 2:00 am onSundays. If one or more allowed TAIs contains time information elementlimited to this period, the UE 52 will be precluded from sending and/orreceiving data outside this period, thus reducing the risk ofunauthorized access to the network by a third party. Further, the RAN 84may detect behaviour that is contrary to the time information elementand use this to detect malicious behaviour that it can report to a CPFincluding, without limitation, the AMF 90, SMF 92 and/or PCF 201. Insome non-limiting examples, the CPF may report detected maliciousbehaviour to the AF 104 that is used by the AS provided to interact withthe mobile network.

In some examples, the PCF 201 may provide multiple RFSP indices in theaccess and mobility policy for radio resource management purposes. Insome examples such RFSP indices may be associated with time informationelement that determines the time period(s) to apply the RFSP index. Foreach RFSP index, if time information element is provided, the RFSP indexwill be enforced only for the time(s) described by the time informationelement. If no time information element is provided, the RFSP index willbe applied irrespective of the time of the UE 52.

With the introduction of the location element and/or time element asparameters upon which one or more access and mobility management policyrules may be conditioned, the PCF 201 may define a flexible access andmobility management policy. By way of non-limiting example:

-   The registration area and/or tracking area may be limited at    different times, reducing signalling to page the UE 52 when an    incoming call arrives;-   Unauthorized calls and/or data connections may be precluded by    specifying at what locations and/or times the UE 52 may access the    network.

Spending Policy

In some examples, the UE 52 may primarily remain in a given location fora large period of time. By way of non-limiting example, a UE 52 mayprimarily remain in an office building during weekdays but may primarilyremain in a suburban or rural residential area during weekends and/orevenings.

In such examples, the NWDAF could identify the location(s) and/ortime(s) during which the UE 52 may most predominantly send or receivedata and provide this information to the PCF 201.

Armed with this information, the PCF 201 may alter a spending policyassociated with the UE 52, including, by way of non-limiting example,providing a higher (or lower) data rate, providing a higher (or lower)data usage cap and/or charging a higher (or lower) per MB rate.

Method Actions

Turning now to FIG. 5, there is shown a flow chart, shown generally at500, of example actions taken at an NF for optimizing the operation of aUE in a network.

One example action 510 is to transmit along the network at least onerule of at least one policy that governs how the UE may exchange packetsalong the network and that contains information conditioned on at leastone information element.

Each rule is considered in decision 520. If information conditioned onthe information element is present in the rule being considered 521,then processing proceeds to decision 530. If not 522, then processingproceeds to action 540.

The information is considered in decision 530. If the information issatisfied by the UE 531, then processing proceeds to action 540. If not532, then processing proceeds to action 550.

An example action 540 is to allow the UE to exchange packets inaccordance with any constraints contained in the at least one rule.

An example action 550 is to preclude the UE from exchanging packets inaccordance with the at least one rule.

The number of rules is considered in decision 560. If more rules shouldbe considered 561, then processing proceeds to decision 520.

Terminology

The terms “including” and “comprising” are used in an open-endedfashion, and thus should be interpreted to mean “including, but notlimited to”. The terms “example” and “exemplary” are used simply toidentify instances for illustrative purposes and should not beinterpreted as limiting the scope of the invention to the statedinstances. In particular, the term “exemplary” should not be interpretedto denote or confer any laudatory, beneficial or other quality to theexpression with which it is used, whether in terms of design,performance or otherwise.

The terms “couple” and “communicate” in any form are intended to meaneither a direct connection or indirect connection through someinterface, device, intermediate component or connection, whetheroptically, electrically, mechanically, chemically, or otherwise.

References in the singular form include the plural and vice versa,unless otherwise noted.

As used herein, relational terms, such as “first” and “second”, andnumbering devices such as “a”, “b” and the like, may be used solely todistinguish one entity or element from another entity or element,without necessarily requiring or implying any physical or logicalrelationship or order between such entities or elements.

General

All statements herein reciting principles, aspects and embodiments ofthe disclosure, as well as specific examples thereof, are intended toencompass both structural and functional equivalents thereof.Additionally, it is intended that such equivalents include bothcurrently known equivalents as well as equivalents developed in thefuture, i.e., any elements developed that perform the same function,regardless of structure.

It should be appreciated that the present disclosure, which can bemodified by omitting, adding or replacing elements with equivalentfunctional elements, provides many applicable inventive concepts thatmay be embodied in a wide variety of specific contexts. The specificembodiments discussed are merely illustrative of specific ways to makeand use the concepts disclosed herein, and do not limit the scope of thepresent disclosure. Rather, the general principles set forth herein areconsidered to be merely illustrative of the scope of the presentdisclosure.

It will be apparent that various modifications and variations coveringalternatives, modifications and equivalents will be apparent to personshaving ordinary skill in the relevant art upon reference to thisdescription and may be made to the embodiments disclosed herein, withoutdeparting from the present disclosure, as defined by the appendedclaims.

Accordingly the specification and the embodiments disclosed therein areto be considered examples only, with a true scope of the disclosurebeing disclosed by the following numbered claims:

What is claimed is:
 1. A method for optimizing operation of a userequipment (UE) in a wireless communications network, the methodperformed at a network function (NF) and comprising: transmitting alongthe network at least one rule of at least one policy that governs howthe UE exchanges packets along the network and that contains informationconditioned on at least one information element, such that: if theinformation conditioned on the at least one information element iscontained in the at least one rule and the UE does not satisfy theinformation contained in the at least one rule, the UE is precluded fromexchanging packets in accordance with the at least one rule; if theinformation conditioned on the at least one information element iscontained in the at least one rule and the UE satisfies the informationcontained in the at least one rule, the UE exchanges packets inaccordance with any constraints contained in the at least one rule; andif there is no information in the at least one rule corresponding to theat least one information element, the UE exchanges packets in accordancewith any constraints contained in the at least one rule.
 2. The methodof claim 1, wherein the at least one information element comprises alocation element.
 3. The method of claim 2, wherein the location elementcomprises at least one of a geographical location specified by a 2Dand/or a 3D coordinate system, a geographical location specified by anidentifier of a geographical zone of a mapping system, a RAN address, acell identifier, a tracking area identifier (TAI), a registration areaidentifier and/or an indication that the at least one rule is alwaysconsidered.
 4. The method of claim 1, wherein the at least oneinformation element comprises a time element.
 5. The method of claim 4,wherein the time element comprises at least one of a time of day, adate, a day of week, a day of month, a month, a year, a periodspecifying at least one of these to start the period and/or at least oneof these to end the period, a recurrence and/or an indication that theat least one rule is always considered.
 6. The method of claim 1,wherein the at least one policy comprises at least one of a UE routeselection policy (URSP), an access network discovery & selection policy(ANDSP), a UE background data transfer policy (UBDTP), an access trafficsteering, switching and splitting (ATSSS) policy, a quality of service(QoS) policy, an access and mobility management policy and a spendingpolicy.
 7. The method of claim 5, wherein the URSP comprises a list ofroute selection descriptors, each route selection descriptor including aroute selection descriptor precedence value that determines the priorityof the route selection descriptor, and one or more of locationinformation element and time information element that respectivelydetermine a location(s) and a time period to apply the route selectiondescriptor.
 8. The method of claim 5, wherein the at least oneinformation element is contained in at least one of the URSP rule and acomponent of a route selection descriptor of the URSP rule, thecomponent comprising at least one of a session continuity (SSC) mode, anetwork slice selection, a data network name (DNN) selection, and anon-seamless off-load indication and/or an access type preference. 9.The method of claim 5, wherein the UBDTP policy specifies at least oneof a UBDTP identification phase for identifying whether the at least oneUE is entitled to UBDTP service; a UBDTP rules definition phase fordefining at least one rule that contains information conditioned on theat least one information element, the at least one rule comprising atleast one of a UBDTP rule and a URSP rule; and a UBDTP applicationserver (AS) configuration phase for identifying the AS associated withthe at least one UE receiving UBDTP service; and a UBDTP operation phasefor providing UBDTP service to background data transferred by the atleast one UE to the AS associated therewith in accordance with the atleast one rule defined in the UBDTP rules definition phase.
 10. Themethod of claim 5, wherein the QoS policy comprises at least one of aQoS profile of a QoS flow for exchange between a session managementfunction (SMF) and a radio access network (RAN) node conditioned on theat least one information element, and a QoS rule for exchange betweenthe SMF and the at least one UE conditioned on the at least oneinformation element and at least one QoS-related information set forexchange between the SMF and a user plane (UP) function (UPF)conditioned on the at least one information element.
 11. The method ofclaim 5, wherein the access and mobility management policy comprises atleast one tracking area identifier (TAI) for exchange between the NF andan operator through an access and mobility management function (AMF)conditioned on the at least one information element.
 12. The method ofclaim 1, wherein the NF comprises a policy and control function (PCF).13. The method of claim 12, wherein the at least one policy comprises atleast one of a UE route selection policy (USRP) and the PCF creates theURSP usable for background data transfer.
 14. The method of claim 12,wherein the PCF sends to a session management function (SMF) of thenetwork, a set of policy charging and control (PCC) rules that includeinformation on handling a UE background data transfer service associatedwith a PDU session.
 15. The method of claim 12, wherein if at least oneof the PCF and a unified data management (UDM) indicate that the UE isentitled to use background data transfer service, and at least one ofthe UBDTP and URSP includes at least one of a location informationelement and a time information element that is not satisfied, the SMFrejects a UE request.
 16. The method of claim 14, wherein the SMFrejects the UE request by sending a reject message to the UE via anapplication management function (AMF) of the network, the reject messageincluding a cause that indicates at least one reason for rejecting theUE request.
 17. The method of claim 16, wherein the at least one reasonincludes at least one of: the UE is not entitled to background datatransfer service, a current UE location does not satisfy a locationinformation element constraint, and a current UE time does not satisfy atime information element constraint.
 18. The method of claim 15,wherein, if the UE is entitled to background data transfer service, theSMF establishes a requested PDU session for transfer of background data.19. The method of claim 18, wherein the SMF checks at least one of thelocation information element and the time information element for thePDU session to determine if the UE is entitled to background datatransfer service.
 20. The method of claim 18, wherein, if the UE is notentitled to the background data transfer service, but at least one ofthe location information element and the time information elementconstraints is not satisfied, the SMF sends a reject message to the AMFthat includes a cause indicating at least one reason that the UE is notentitled to the background data transfer service.
 21. The method ofclaim 18, wherein, if the UE is entitled to the background data transferservice, and the location and time information element constraints aresatisfied, at least one of the SMF and the PCF monitors the location andtime information elements for the duration of the PDU session of thebackground data transfer.
 22. The method of claim 20, wherein based onthe monitoring, the SMF determines that at least one of the locationinformation element and the time information element is not satisfied,the SMF initiates a PDU session release procedure.
 23. The method ofclaim 22 wherein the SMF initiates the PDU session release procedureupon a request of the PCF due to a violation of the at least one of thetime and location information element constraints.
 24. The method ofclaim 22, wherein the SMF initiates a user plane (UP) deactivation of aUP connection of an existing PDU session.
 25. The method of claim 20,wherein the at least one of the location information element and thetime information element constraints is not satisfied as a result of aUE mobility and handover transition.
 26. The method of claim 1, furthercomprising including at least one indication that stipulates whether theat least one rule is strictly enforced.
 27. The method of claim 1,wherein the network includes an application function (AF) that specifiesat least one of network area information and time window information,the AF includes the at least one indication as to whether the at leastone of network area information and time window information will bestrictly enforced.
 28. The method of claim 27, wherein if the at leastone indication stipulates that the at least one rule will be strictlyenforced, if the UE does not satisfy the information contained in the atleast one rule, then the UE is precluded from exchanging packets inaccordance with the at least one rule.
 29. The method of claim 27,wherein if the at least one indication stipulates that the at least onerule will not be strictly enforced, even if the UE does not satisfy theinformation contained in the at least rule, the UE exchanges packets inaccordance with any constraints contained in the at least one rule. 30.The method of claim 12, wherein the PCF sends a UE route selectionpolicy (USRP) when a condition pertaining to at least one of a timeperiod and a location is met.
 31. The method of claim 14, wherein, whenthe condition pertaining to at least one of a time period and a locationis met, the UE performs one of establishing a PDU session and activatinga UP connection of an existing PDU session to couple to a data networkname (DNN) selection for use of network services provided therein. 32.The method of claim 14, wherein, if the UE exchanges packets even thoughthe UE does not satisfy the information in the at least one rule, adifferent criterion is applied to packets exchanged in accordance withthe at least one rule.
 33. The method of claim 32 wherein the criterionis at least one of a different charging rate and a different quality ofservice (QoS).
 34. The method of claim 15 wherein if UE configurationdata indicates that the UE is entitled to use the background datatransfer service, but the PCF confirms that at least one of a locationinformation element and a time information element is not satisfied, atleast one of the PCF and the UDM sends a response to the SMF indicatingone of acceptance indication and rejection indication to a SMF requestfor data association dedicated to PDU Session establishment.
 35. Anetwork function (NF) comprising: a processor; and a non-transientmemory for storing instructions that when executed by the processorcause the NF to optimize operation of a user equipment (UE) in thenetwork, by: transmitting along the network at least one rule of atleast one policy that governs how the UE exchanges packets along thenetwork and that contains information conditioned on at least oneinformation element, such that: if the information conditioned on the atleast one information element is contained in the at least one rule andthe UE does not satisfy the information contained in the at least onerule, the UE is be precluded from exchanging packets in accordance withthe at least one rule; if the information conditioned on the at leastone information element is contained in the at least one rule and the UEsatisfies the information contained in the at least one rule, the UEexchanges packets in accordance with any constraints contained in the atleast one rule; and if there is no information in the at least one rulecorresponding to the at least one information element, the UE exchangespackets in accordance with any constraints contained in the at least onerule.
 36. A system comprising a network function (NF), wherein the NF isconfigured to optimize operation of a user equipment (UE) in thenetwork, by: transmitting along the network at least one rule of atleast one policy that governs how the UE exchanges packets along thenetwork and that contains information conditioned on at least oneinformation element, such that: if the information conditioned on the atleast one information element is contained in the at least one rule andthe UE does not satisfy the information contained in the at least onerule, the UE is be precluded from exchanging packets in accordance withthe at least one rule; if the information conditioned on the at leastone information element is contained in the at least one rule and the UEsatisfies the information contained in the at least one rule, the UEexchanges packets in accordance with any constraints contained in the atleast one rule; and if there is no information in the at least one rulecorresponding to the at least one information element, the UE exchangespackets in accordance with any constraints contained in the at least onerule.